| To: | hank peng <pengxihan@xxxxxxxxx> |
|---|---|
| Subject: | Re: How to solve "No space left" problem on my 32bit machine? |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Sun, 26 Jul 2009 20:48:11 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <389deec70907252030s3524b2ecj9b35da9ea376020f@xxxxxxxxxxxxxx> |
| References: | <389deec70907252030s3524b2ecj9b35da9ea376020f@xxxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.22 (Macintosh/20090605) |
hank peng wrote: > Hi, folks: > I have a 2.5T file system formatted with XFS, df tells me it still > have about 10G space available, but I can't create new files or > directory any more. Return message is "No space left on this device". > I searched solution for this problem through google, and found this: > http://oss.sgi.com/archives/xfs/2005-06/msg00347.html. I think it is a > known "No space left" problem. I wonder whether it can only > be solved on 64-bit machine? If on my 32-bit machine, what should I do? On very recent kernels you can use 64-bit inodes on 32-bit machines; you can try mounting with -o inode64 t allow this. Be warned though that some applications use 32-bit stat calls still, rather than 64-bit variants, and you may have some problems. You should file bugs against any such applications that you find... -eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs_repair: check for null single-block dir buffer pointer in phase6, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH 1/9] xfs: avoid memory allocation under m_peraglock in growfs code, Felix Blyakher |
| Previous by Thread: | Re: How to solve "No space left" problem on my 32bit machine?, Emmanuel Florac |
| Next by Thread: | Re: How to solve "No space left" problem on my 32bit machine?, hank peng |
| Indexes: | [Date] [Thread] [Top] [All Lists] |