From: Eric Sandeen <sandeen@sandeen.net>
To: Samuel Granjeaud <samuel.granjeaud@inserm.fr>, xfs@oss.sgi.com
Subject: Re: Run out of inodes?
Date: Fri, 29 Aug 2014 10:02:27 -0500 [thread overview]
Message-ID: <54009603.9050404@sandeen.net> (raw)
In-Reply-To: <5400802C.5050005@inserm.fr>
On 8/29/14, 8:29 AM, Samuel Granjeaud wrote:
> Taking into account the two answers, here is some more information.
>
> The system is a openfiler installation, v2.3, up-to-date.
> https://www.openfiler.com/community/download
>
> The problematic system is a backup but the production system uses the same openfiler NAS system. The difference is that there are currently more files on the backup system than the production system; so I guess the problem will appear sooner on the prod sys.
>
> # xfs_info /dev/vg1_backup/backup
> meta-data=/mnt/vg1_backup/backup isize=256 agcount=80, agsize=58981376 blks
> = sectsz=512
> data = bsize=4096 blocks=4718510080, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=1
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=32768, version=1
> = sectsz=512 sunit=0 blks
> realtime =none extsz=65536 blocks=0, rtextents=0
>
> # uname -a
> Linux 2.6.26.8-1.0.11.smp.gcc3.4.x86_64 #1 SMP Sun Jan 11 02:42:55 GMT 2009 x86_64 x86_64 x86_64 GNU/Linux
>
> # xfs_info -V /dev/vg1_backup/backup
> xfs_info version 2.6.25
>
> # cat /etc/fstab
> ...
> /dev/vg1/pcurrent /mnt/vg1/pcurrent xfs defaults,usrquota,grpquota 0 0
>
> # cat /etc/mtab
> ...
> /dev/mapper/vg1-pcurrent /mnt/vg1/pcurrent xfs rw,usrquota,grpquota 0 0
<thanks for all the extra info>
> I have no idea concerning the inode64 option. Just tell me how to find it out. I don't think this option was changed: as previously told, removing a few files allows files to be created without error.
You'll want to be using the inode64 mount option for this filesystem; I'm surprised the openfiler folks didn't do this by default.
http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F
add it to fstab for this filesystem, reboot the box (or unmount/mount the filesystem) and all should be well.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-08-29 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 10:08 Run out of inodes? Samuel Granjeaud
2014-08-29 11:43 ` Emmanuel Florac
2014-08-29 11:48 ` Brian Foster
2014-08-29 13:29 ` Samuel Granjeaud
2014-08-29 15:02 ` Eric Sandeen [this message]
2014-08-29 15:22 ` Samuel Granjeaud
2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM
2014-08-31 2:46 ` Eric Sandeen
2014-09-01 19:19 ` Emmanuel Florac
2014-09-02 7:22 ` Samuel Granjeaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54009603.9050404@sandeen.net \
--to=sandeen@sandeen.net \
--cc=samuel.granjeaud@inserm.fr \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox