| To: | Juri Haberland <juri@xxxxxxxxxxxxxx>, Florin Andrei <florin@xxxxxxx> |
|---|---|
| Subject: | Re: files in /etc/xinetd.d become 0 byte size |
| From: | Seth Mos <knuffie@xxxxxxxxx> |
| Date: | Tue, 26 Mar 2002 22:48:15 +0100 |
| Cc: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>, linux-xfs <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <3CA0E904.1080907@xxxxxxxxxxxxxx> |
| References: | <3C961055.FF5DF9C6@xxxxxxxxxxxxxxxx> <1017176697.16815.21.camel@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
At 22:32 26-3-2002 +0100, Juri Haberland wrote: Ahm, Florin, I think that the conclusion of this thread was that even multiple syncs don't help - instead you could just use 'sleep 30'. The bug must be somewhere in the kernel and it would be nice to know, whether it shows up with ext2/3 also or not. And also 2.4.18 just works with the same init script without the need of just a single 'sync' or 'sleep 30'... I believe this occured on a software raid 1 root filesystem.And doing a sync before remounting may be called overkill but I have absolutely no objection to it being there. It can only do good there and I can't see how this could be harmfull in any way. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. |
| Previous by Date: | Re: files in /etc/xinetd.d become 0 byte size, Juri Haberland |
|---|---|
| Next by Date: | Re: files in /etc/xinetd.d become 0 byte size, Florin Andrei |
| Previous by Thread: | Re: files in /etc/xinetd.d become 0 byte size, Juri Haberland |
| Next by Thread: | Re: files in /etc/xinetd.d become 0 byte size, Florin Andrei |
| Indexes: | [Date] [Thread] [Top] [All Lists] |