| To: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS recovery on root filesystem |
| From: | Sean Neakums <sneakums@xxxxxxxx> |
| Date: | Thu, 25 Apr 2002 16:59:29 +0100 |
| In-reply-to: | <3CC81FB9.3803729D@xxxxxxxxxxxxxxxx> (Simon Matter's message of "Thu, 25 Apr 2002 17:24:41 +0200") |
| Mail-followup-to: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
| References: | <Pine.LNX.4.33.0204251049450.1201-100000@xxxxxxxxxxxx> <3CC81FB9.3803729D@xxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) |
commence Simon Matter quotation: > I guess you have also updated glibc. IIRC when updating glibc, the > root fs can not be unmounted properly (remount readonly) on shutdown > and therefore you'll notice recovery on the first boot after glibc > upgrade. It has always been like this and was very annoying with > big root fs on ext2 :) I'm sure it's not kernel related. I have never seen this happen after glibc upgrades on Debian systems, and I can't think of a reason why it should happen at all. Steve's suggestion that it's the readonly-remount-path bug sounds a lot more plausible. -- ///////////////// | | The spark of a pin <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS recovery on root filesystem, Simon Matter |
|---|---|
| Next by Date: | Re: XFS recovery on root filesystem, Steve Lord |
| Previous by Thread: | Re: XFS recovery on root filesystem, Simon Matter |
| Next by Thread: | Re: XFS recovery on root filesystem, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |