| To: | Cedric - Equinoxe Media <cedric@xxxxxx> |
|---|---|
| Subject: | Re: xfs crash |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Wed, 7 Nov 2007 07:55:56 +1100 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20071106160721.GB25295@e-m.fr> |
| References: | <20071105215135.GA12238@e-m.fr> <20071106082632.GU995458@sgi.com> <20071106092157.GB16694@e-m.fr> <20071106160721.GB25295@e-m.fr> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Tue, Nov 06, 2007 at 05:07:21PM +0100, Cedric - Equinoxe Media wrote: > I just had exactly the same crash again today : > /dev/sda4 on /filer type xfs (rw,noexec,nosuid,nodev,noatime) What did xfs_check tell you about the corruption? > Seems to be again on a setattr() ? Doing a truncation freeing some blocks. What is the client doing (i.e. io patterns, application, etc) to cause this? can you reproduce it without NFS being used? To track this down I'm going to need a reproducable test case.... Seeing this is a brand new server, have you run and soak or stress test on the raw storage to confirm it is error free? Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TAKE 972756 - Implement fallocate., David Chinner |
|---|---|
| Next by Date: | Re: TAKE 972756 - Implement fallocate., Nathan Scott |
| Previous by Thread: | Re: xfs crash, Cedric - Equinoxe Media |
| Next by Thread: | Re: xfs crash, Cedric - Equinoxe Media |
| Indexes: | [Date] [Thread] [Top] [All Lists] |