xfs
[Top] [All Lists]

Re: False No space left on device error

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
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <BE5986C67D271E4EA72B61F406AB91F29C7C86@sbapexch02.ad.corp.expertcity.com>
References: <BE5986C67D271E4EA72B61F406AB91F29C7C86@sbapexch02.ad.corp.expertcity.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
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 d

Well 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?)


-Eric

Michael Ramsey




<Prev in Thread] Current Thread [Next in Thread>