| To: | Lauri Ojantakanen <lauri@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Questions about recovery |
| From: | Seth Mos <knuffie@xxxxxxxxx> |
| Date: | Thu, 17 May 2001 10:50:32 +0200 |
| In-reply-to: | <01051710262100.02801@lauri-ibm> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
At 10:26 17-5-2001 +0300, Lauri Ojantakanen wrote:
Hi, hmmm... I remember that at some point kupdate got stuck on my machine and I could not reboot the machine or sync the filessystem. If that happened I noticed that files that were edited ot touched after the kupdate hung would get a "\0" in it after recovery. In the case of /etc/fstab it gave some very weird results. It took some time to notice because the rest of the system continued to function. The cause of it was eventually lead back to a bad ram stick. The 2.2 kernel before that obviously was not pushing the ram hard enough to expose it. I have not seen it after replacing the bad ram stick. This may not be the case here but I am just giving a explanation of what I did to make it produce those errors. 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Questions about recovery, Lauri Ojantakanen |
|---|---|
| Next by Date: | Re: Samba ACLs - Latest Samba & XFS CVS, Klaus Strebel,ITS,204 |
| Previous by Thread: | Questions about recovery, Lauri Ojantakanen |
| Next by Thread: | Re: Questions about recovery, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |