|To:||Michael Ramsey <Michael.Ramsey@xxxxxxxxxx>|
|Subject:||Re: False No space left on device error|
|From:||Eric Sandeen <sandeen@xxxxxxx>|
|Date:||Wed, 01 Jun 2005 22:41:14 -0500|
|User-agent:||Mozilla Thunderbird 1.0.2 (Macintosh/20050317)|
Michael Ramsey wrote:
logfs2.nyc#mount /dev/mapper/raidvol-vol1 on /u01 type xfs (rw,inode64) logfs2.nyc#touch a logfs2.nyc#touch b logfs2.nyc#touch c logfs2.nyc#touch dWell looks like the initial test worked...
great, I thought that was probably it.
What to do what to do... QA perhaps? I will run some tests and see if I lose any data...
you can use the undocumented/unsupported/non-production "ino64" option to force all inodes into 64-bit range, and test them on a (smaller) scratch fs. I expect that it'll be fine but testing is good.
Will xfs_recover work with 64 bit inodes?
all the xfs tools should be fine w/ 64-bit inodes on a 64-bit system. (Hm, but opteron is tricky, were they built as 64-bit?)
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||RE: False No space left on device error, Michael Ramsey|
|Next by Date:||TAKE 907752 - xfstests, FSG QA|
|Previous by Thread:||RE: False No space left on device error, Michael Ramsey|
|Next by Thread:||Re: False No space left on device error, Jan Derfinak|
|Indexes:||[Date] [Thread] [Top] [All Lists]|