Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs\s+hang\s+when\s+filesystem\s+filled\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs\s+hang\s+when\s+filesystem\s+filled\s*$/: 8 ]

Total 8 documents matching your query.

1. xfs hang when filesystem filled (score: 1): Author: "Guk-Bong, Kwon" <gbkwon@xxxxxxxxx>; Date: Tue, 7 Aug 2012 14:54:48 +0900; HI all I tested xfs over nfs using bonnie++ xfs and nfs hang when xfs filesystem filled What's the problem? see below -- 1. nfs server a. uname -a - Linux nfs_server 2.6.32.58 #1 SMP Thu Mar 22 13:33; /archives/xfs/2012-08/msg00062.html (45,986 bytes)
2. RE: xfs hang when filesystem filled (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Tue, 7 Aug 2012 09:05:32 +0000; Hi Kwon, I'd suggest that the asynchronous nature of NFS means that you've got all the nfs threads on the client waiting on a response from the NFS server. The server is in trouble because you've no; /archives/xfs/2012-08/msg00064.html (47,574 bytes)
3. Re: xfs hang when filesystem filled (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Tue, 07 Aug 2012 12:18:07 +0200; Am Dienstag, 7. August 2012, 14:54:48 schrieb Guk-Bong, Kwon: You should never ever come into this situation. What else than a hang would you expect? Should the server crash instead? A filesystem sho; /archives/xfs/2012-08/msg00065.html (8,315 bytes)
4. Re: xfs hang when filesystem filled (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Tue, 07 Aug 2012 08:04:28 -0500; The problem is likely the OP has been given enough rope to hang himself. ;) ~90GB device 4096*23592960/1048576/1000= ~92GB filesystem ((((200*1024=204800 files)*(1024000 bytes))/1048576)/1000)= ~200G; /archives/xfs/2012-08/msg00066.html (9,111 bytes)
5. Re: xfs hang when filesystem filled (score: 1): Author: "Guk-Bong, Kwon" <gbkwon@xxxxxxxxx>; Date: Wed, 8 Aug 2012 16:55:47 +0900; why server hang or reset ? I expect some warning/error message like "No space left on device" and then I hope server is ok 2012/8/7 Burbidge, Simon A <s.burbidge@xxxxxxxxxxxxxx>:; /archives/xfs/2012-08/msg00071.html (58,389 bytes)
6. Re: xfs hang when filesystem filled (score: 1): Author: Dave Howorth <dhoworth@xxxxxxxxxxxxxxxxx>; Date: Wed, 08 Aug 2012 11:08:10 +0100; NFS has always been awkward in limit conditions like this. People just learn to stay away from such boundary conditions if they want reliable servers, for this and other good reasons already mentione; /archives/xfs/2012-08/msg00072.html (9,696 bytes)
7. RE: xfs hang when filesystem filled (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Wed, 8 Aug 2012 10:28:00 +0000; As I understand it, NFS does not have the error reporting pathways to accommodate sending back a "no apace" message to the user process. There isn't a direct link between user files and processes and; /archives/xfs/2012-08/msg00073.html (65,610 bytes)
8. Re: xfs hang when filesystem filled (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 9 Aug 2012 08:23:05 +1000; It appears to be blocked in writeback, getting ENOSPC errors when they shouldn't occur. Old kernel. Upgrade. You're using the async export option, which means the server/client write throttling mecha; /archives/xfs/2012-08/msg00077.html (14,309 bytes)

Current List: 1 - 8
Page: [1]