Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ENOSPC\s+at\s+90\%\s+with\s+plenty\s+of\s+inodes\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ENOSPC\s+at\s+90\%\s+with\s+plenty\s+of\s+inodes\s*$/: 13 ]

Total 13 documents matching your query.

1. ENOSPC at 90% with plenty of inodes (score: 1): Author: James Braid <jamesb@xxxxxxxxxxxx>; Date: Fri, 8 Oct 2010 18:17:52 +0100; Hi, On a fairly busy mail server hosting about 1000 cyrus mailboxes (each message is stored as a separate file), we are observing ENOSPC errors from the cyrus pop/imap daemons when attempting to crea; /archives/xfs/2010-10/msg00107.html (6,835 bytes)
2. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Richard Scobie <richard@xxxxxxxxxxx>; Date: Sat, 09 Oct 2010 09:33:34 +1300; Hi James, You're not hitting this issue are you? <http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F> Regards, Richard; /archives/xfs/2010-10/msg00108.html (7,089 bytes)
3. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>; Date: Fri, 8 Oct 2010 22:40:57 +0200; Le Fri, 8 Oct 2010 18:17:52 +0100 vous écriviez: You must be running out of inodes, this probably should be a FAQ... Check with xfs_info how much space is dedicated to inodes, and expand it with xfs_; /archives/xfs/2010-10/msg00109.html (8,323 bytes)
4. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>; Date: Fri, 8 Oct 2010 22:43:45 +0200; Le Fri, 8 Oct 2010 18:17:52 +0100 vous écriviez: I forgot a point : 10% is NOT plenty of space. At 90%, a filesystem must be considered full, particularly with lots of inodes, even if the available s; /archives/xfs/2010-10/msg00110.html (8,189 bytes)
5. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Sat, 9 Oct 2010 09:51:46 +1100; Sounds like fragmented free space. What is the output of: xfs_db -r -c "freesp -s" <device> Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx; /archives/xfs/2010-10/msg00111.html (8,916 bytes)
6. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: James Braid <jamesb@xxxxxxxxxxxx>; Date: Mon, 11 Oct 2010 15:03:28 +0100; from to extents blocks pct 1 1 2298052 2298052 40.52 2 3 1568338 3337017 58.84 4 7 8432 35716 0.63 8 15 50 423 0.01 total free extents 3874872 total free blocks 5671208 average free extent size 1.463; /archives/xfs/2010-10/msg00126.html (8,329 bytes)
7. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 12 Oct 2010 09:35:07 +1100; The error has nothing to do with the size of the files, but everything to do with being able to allocate more inodes. Inode allocation requires 4 contiguous blocks (for 256 byte inodes, more for larg; /archives/xfs/2010-10/msg00127.html (9,722 bytes)
8. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Mon, 11 Oct 2010 20:27:00 -0500; Dave Chinner put forth on 10/11/2010 5:35 PM: Hay Dave, would a "backup/reformat/restore" help with free space fragmentation in this case? If so, could/should the OP specify anything during the mkfs.; /archives/xfs/2010-10/msg00128.html (10,634 bytes)
9. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 12 Oct 2010 21:29:54 +1100; Of course. But that's the last resort.... No. These problems usually appear in filesystems that have run at greater than 85-90% full for extended periods of time without being emptied at all. Once yo; /archives/xfs/2010-10/msg00130.html (11,511 bytes)
10. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Tue, 12 Oct 2010 15:52:40 +0200; I'm curious if using noikeep mount option has any effect on free space fragmentation? jan; /archives/xfs/2010-10/msg00131.html (9,642 bytes)
11. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Oct 2010 18:21:42 -0500; Dave Chinner put forth on 10/12/2010 5:29 AM: So, given that this problem is on a production IMAP server, and the OP likely can't just willy nilly start deleting user files, would adding more disk (a; /archives/xfs/2010-10/msg00136.html (12,630 bytes)
12. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 13 Oct 2010 11:25:09 +1100; As long as you are unsing inode64 then growing the filesystem will alow more inodes to be allocated. Sure, that'd work, too. Fundamentally, moving data and inodes around after a grow (or new filesyst; /archives/xfs/2010-10/msg00137.html (13,774 bytes)
13. Re: ENOSPC at 90% with plenty of inodes (score: 1): Author: XIE Zhengmao <zhengmaoxie@xxxxxxxxx>; Date: Wed, 24 Nov 2010 01:04:35 +0000 (UTC); "no space left" when your still have space and inodes... Please fsck the file system, too many fs errors cause this problem.; /archives/xfs/2010-11/msg00364.html (6,562 bytes)

Current List: 1 - 13
Page: [1]