Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*False\s+No\s+space\s+left\s+on\s+device\s+error\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*False\s+No\s+space\s+left\s+on\s+device\s+error\s*$/: 30 ]

Total 30 documents matching your query.

1. False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:15:40 -0700; Linux logfs2.nyc 2.6.11-1.27_FC3smp #1 SMP Tue May 17 20:38:05 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux logfs2.nyc#df -h /dev/mapper/raidvol-vol1 9.0T 7.1T 2.0T 79% /u01 logfs2.nyc#rpm -qa |grep xfs; /archives/xfs/2005-06/msg00003.html (8,716 bytes)
2. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Wed, 01 Jun 2005 18:39:06 -0500; My best guess is that this is the inode32 allocator running out of < 2T blocks to allocate inodes... I'd have to think about how to prove this theory. -Eric Michael Ramsey wrote: logfs2.nyc#uname -a; /archives/xfs/2005-06/msg00005.html (9,897 bytes)
3. Re: False No space left on device error (score: 1): Author: Net Llama! <netllama@xxxxxxxxxxxxx>; Date: Wed, 1 Jun 2005 17:35:49 -0500 (EST); Have you run xfs_repair on this partition? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@xxxxxxxxxxxxx LlamaLand http://netllama.linux-sxs.org; /archives/xfs/2005-06/msg00007.html (10,069 bytes)
4. RE: False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:43:05 -0700; Yes. The error returns. Could this be a 8K stack issue under Fedora x86_64? Michael Ramsey Have you run xfs_repair on this partition? 1% /u01 logfs2.nyc#rm a -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~; /archives/xfs/2005-06/msg00008.html (10,342 bytes)
5. RE: False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:45:26 -0700; Even under the x86_64 kernel? Michael Ramsey My best guess is that this is the inode32 allocator running out of < 2T blocks to allocate inodes... I'd have to think about how to prove this theory. -Er; /archives/xfs/2005-06/msg00009.html (10,300 bytes)
6. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Wed, 01 Jun 2005 21:19:43 -0500; Michael Ramsey wrote: Even under the x86_64 kernel? even that kernel uses 32 bit inodes by default... 64-bit inodes -should- be safe on x86_64; an interesting test would be to mount with the inode64; /archives/xfs/2005-06/msg00011.html (11,697 bytes)
7. RE: False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 19:54:32 -0700; /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... What to do what to do...; /archives/xfs/2005-06/msg00012.html (11,625 bytes)
8. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Wed, 01 Jun 2005 22:41:14 -0500; /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; /archives/xfs/2005-06/msg00013.html (10,292 bytes)
9. Re: False No space left on device error (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Thu, 2 Jun 2005 14:52:07 +0200 (CEST); Hi. Is it possible to explain it little bit more? There is no info in xfs.txt. Thanks. Jan --; /archives/xfs/2005-06/msg00018.html (9,382 bytes)
10. Re: False No space left on device error (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Thu, 02 Jun 2005 08:19:15 -0500; ino64 is a test option, it deliberately adds a large number to inode values so that it is possible to test that the inode handling is 64 bit clean without buying a few Tbytes of disk (which would hav; /archives/xfs/2005-06/msg00019.html (10,968 bytes)
11. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Thu, 02 Jun 2005 08:26:54 -0500; Jan Derfinak wrote: On Wed, 1 Jun 2005, Eric Sandeen wrote: Hi. you can use the undocumented/unsupported/non-production "ino64" option to force all inodes into 64-bit range, and test them on a (small; /archives/xfs/2005-06/msg00020.html (10,394 bytes)
12. Re: False No space left on device error (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Thu, 02 Jun 2005 08:29:07 -0500; Steve Lord wrote: ino64 is a test option, it deliberately adds a large number to inode values so that it is possible to test that the inode handling is 64 bit clean without buying a few Tbytes of dis; /archives/xfs/2005-06/msg00021.html (10,314 bytes)
13. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Thu, 02 Jun 2005 08:30:39 -0500; Steve Lord wrote: ino64 is a test option, it deliberately adds a large number to inode values so that it is possible to test that the inode handling is 64 bit clean without buying a few Tbytes of dis; /archives/xfs/2005-06/msg00022.html (10,565 bytes)
14. Re: False No space left on device error (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Thu, 2 Jun 2005 11:44:15 -0700; maybe s/ino64/force_no64/ then?; /archives/xfs/2005-06/msg00025.html (9,076 bytes)
15. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Thu, 02 Jun 2005 14:07:46 -0500; Chris Wedgwood wrote: On Thu, Jun 02, 2005 at 08:26:54AM -0500, Eric Sandeen wrote: ino64 is testing only; it artificially forces ALL inodes into 64 bits. maybe s/ino64/force_no64/ then? ah, ino64 ha; /archives/xfs/2005-06/msg00026.html (9,842 bytes)
16. False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:15:40 -0700; Linux logfs2.nyc 2.6.11-1.27_FC3smp #1 SMP Tue May 17 20:38:05 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux logfs2.nyc#df -h /dev/mapper/raidvol-vol1 9.0T 7.1T 2.0T 79% /u01 logfs2.nyc#rpm -qa |grep xfs; /archives/xfs/2005-06/msg00175.html (8,716 bytes)
17. Re: False No space left on device error (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Wed, 01 Jun 2005 18:39:06 -0500; My best guess is that this is the inode32 allocator running out of < 2T blocks to allocate inodes... I'd have to think about how to prove this theory. -Eric Michael Ramsey wrote: logfs2.nyc#uname -a; /archives/xfs/2005-06/msg00177.html (9,897 bytes)
18. Re: False No space left on device error (score: 1): Author: Net Llama! <netllama@xxxxxxxxxxxxx>; Date: Wed, 1 Jun 2005 17:35:49 -0500 (EST); Have you run xfs_repair on this partition? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@xxxxxxxxxxxxx LlamaLand http://netllama.linux-sxs.org; /archives/xfs/2005-06/msg00179.html (10,069 bytes)
19. RE: False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:43:05 -0700; Yes. The error returns. Could this be a 8K stack issue under Fedora x86_64? Michael Ramsey Have you run xfs_repair on this partition? 1% /u01 logfs2.nyc#rm a -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~; /archives/xfs/2005-06/msg00180.html (10,342 bytes)
20. RE: False No space left on device error (score: 1): Author: "Michael Ramsey" <Michael.Ramsey@xxxxxxxxxx>; Date: Wed, 1 Jun 2005 16:45:26 -0700; Even under the x86_64 kernel? Michael Ramsey My best guess is that this is the inode32 allocator running out of < 2T blocks to allocate inodes... I'd have to think about how to prove this theory. -Er; /archives/xfs/2005-06/msg00181.html (10,300 bytes)

Current List: 1 - 20
Page: [1] [2]