| To: | Chris Seufert <seufert@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS Journal on md device |
| From: | martin f krafft <madduck@xxxxxxxxxxx> |
| Date: | Wed, 6 Sep 2006 05:40:27 +0200 |
| Cc: | "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <2260b150609051853w1286eda7ve59a5df2c7e0ae1c@mail.gmail.com> |
| Mail-followup-to: | Chris Seufert <seufert@xxxxxxxxx>, "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| References: | <2260b150609051640y288629cbtcbc133d05b2b40dd@mail.gmail.com> <44FE28A8.5000803@oss.sgi.com> <2260b150609051853w1286eda7ve59a5df2c7e0ae1c@mail.gmail.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
also sprach Chris Seufert <seufert@xxxxxxxxx> [2006.09.06.0353 +0200]: > However on reboot xfs does a journal rebuild/repair. and the md > does a re-sync of the md device. Which distro? I am the Debian maintainer for mdadm and have run into the problem that the array used for / cannot be stopped until after / is unmounted, at which point nothing stops the array for there is no shutdownramfs. However, we (Debian) remount / read-only and I never see a filesystem check on reboot. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus@xxxxxxxxxxx the micro$oft hoover: finally, a product that's supposed to suck!
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS Journal on md device, martin f krafft |
|---|---|
| Next by Date: | Bad block on partition, how to deal with it?, Vijay Gill |
| Previous by Thread: | XFS Journal on md device, Chris Seufert |
| Next by Thread: | Re: XFS Journal on md device, Chris Seufert |
| Indexes: | [Date] [Thread] [Top] [All Lists] |