| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: False No space left on device error |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Thu, 02 Jun 2005 08:30:39 -0500 |
| Cc: | Jan Derfinak <ja@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <429F0753.5010403@xfs.org> |
| References: | <BE5986C67D271E4EA72B61F406AB91F29C7C86@sbapexch02.ad.corp.expertcity.com> <429E7FDA.7070307@sgi.com> <Pine.LNX.4.58.0506021444230.18757@alienAngel.home.sk> <429F0753.5010403@xfs.org> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0.2 (Macintosh/20050317) |
Steve Lord wrote:
well, the inode64 option itself is the -inverse- of the hack, actually, right. Default XFS inode allocation changed a few years ago, to force inodes into the low 32-bit range. THAT was the mild hack, and the inode64 option was added to again allow XFS to work as originally designed, allocating inodes anywhere on the filesystem on systems which could handle 64-bit inodes. -Eric Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: False No space left on device error, Steve Lord |
|---|---|
| Next by Date: | Re: XFS module for RHEL4, Sonny Rao |
| Previous by Thread: | Re: False No space left on device error, Steve Lord |
| Next by Thread: | Re: False No space left on device error, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |