Re: msg00264; Cant create new files

["Shinya Sakamoto" <sakamoto@xxxxxxxxx>]

Hello Dave,

Thanks for your response.
`df -i` and `-k` were listed below. We have four 2TB and a 0.9TB. The 
problem was only in /dev/pool/lvol2. # of inodes seemed to be fine. # of 
files/directories were almost 5000.

# df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/pool/lvol1      2147287040 2146338596    948444 100% /shares/nas3_0
/dev/pool/lvol2      2147287040 1214659232 932627808  57% /shares/nas3_1
/dev/pool/lvol3      2147287040 1577714296 569572744  74% /shares/nas3_2
/dev/pool/lvol4      2147287040 1651783800 495503240  77% /shares/nas3_3
/dev/pool/lvol5      933511888 787869104 145642784  85% /shares/nas3_4

# df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/pool/lvol1      3820400   17414 3802986    1% /shares/nas3_0
/dev/pool/lvol2      4294967295    5824 4294961471    1% /shares/nas3_1
/dev/pool/lvol3      4294967295   31879 4294935416    1% /shares/nas3_2
/dev/pool/lvol4      1982069792   16476 1982053316    1% /shares/nas3_3
/dev/pool/lvol5      582608256   14384 582593872    1% /shares/nas3_4

As you may guess, we have already abandon to fix it. Once we backup data, 
eliminated only the lvol2 and make it again, then restore data. Now, the 
lvol2 works fine, it can be create files even if the # of files is greater 
than used to be. So, I would like to know what was the cause and if there 
was other solution or not.

I wonder if there might be a bug which `df -i` think inodes available but 
actually no inodes. Could you please advise us if you have such a 
information?

Best regards,
Shinya Sakamoto

----- Original Message ----- 
From: "Dave Chinner" <dgc@xxxxxxx>
To: "Shinya Sakamoto" <sakamoto@xxxxxxxxx>
Cc: <linux-xfs@xxxxxxxxxxx>
Sent: Thursday, May 26, 2005 12:07 PM
Subject: Re: msg00264; Cant create new files


> On Thu, May 26, 2005 at 11:47:08AM +0900, Shinya Sakamoto wrote:
> > Hello all,
> >
> > Our xfs fileserver had a trouble. It was unable to create a file with "no
> > space left on device" message but had 0.6TB (40%) space available. When 
> > we
> > delete one file, we can create one file. In other words, it was unable to
> > increase in number of files/directories. xfs_check and xfs_repair results 
> > no
> > errors and no fixes.
>
> Sounds like you've run out of inode space. what does `df -i` tell you?
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> R&D Software Engineer
> SGI Australian Software Group