| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: server crashing |
| From: | Artur Makówka <juice@xxxxxxxxxxxxx> |
| Date: | Thu, 13 Apr 2006 13:00:52 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20060412020427.GI1484909@melbourne.sgi.com> |
| References: | <443627B1.5090100@ursynow.2a.pl> <20060410015916.GK2732@melbourne.sgi.com> <443B60E8.6070004@ursynow.2a.pl> <20060412020427.GI1484909@melbourne.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5 (Windows/20051201) |
David Chinner napisal(a):
On Tue, Apr 11, 2006 at 09:55:20AM +0200, Artur Makówka wrote:and why xfs_repair didnt repaired it ? i can't run it so often, because to run it i think i have to unmount my filesystem. and of course this means longer downtime for my users, which for now i just can't do. Maybe there is some kind of bug with this situation, because i forgot to tell you one thing: i have one more XFS partition that is inside this one big XFS partition. its in fstab like this: /var/eaccelerator /eaccelerator xfs loop 0 0 and i did /var/eaccelerator with dd ( dd if=/dev/zero of=/var/eaccelerator ) with size of 1GB. i deleted it for test purposes, and it didnt crash yet (but that doesnt mean anything, there were already times of 5 and more days working without crash and then suddenly it was happening) so, does this loop partition can have anything to do ? i will run xfs_check in a few days, unless there is a way to run it on mounted partition without the risk of wrong corruption reports |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: howto preallocate to minimize fragmentation, Stewart Smith |
|---|---|
| Next by Date: | Re: 2.6.17-rc1 did break XFS, Jan Engelhardt |
| Previous by Thread: | Re: server crashing, David Chinner |
| Next by Thread: | Re: server crashing, Artur Makówka |
| Indexes: | [Date] [Thread] [Top] [All Lists] |