Messages in this thread | | | Date | Mon, 2 Feb 2004 09:34:39 -0500 | From | Daniel Jacobowitz <> | Subject | Re: RAID arrays not reconstructing in 2.6 |
| |
On Mon, Feb 02, 2004 at 03:46:49PM +1100, Neil Brown wrote: > On Sunday February 1, dan@debian.org wrote: > > I saw this a couple of weeks ago in a 2.6.0-test kernel, and today in > > 2.6.2-rc3. When I have to hit the hard reset button on my desktop, whose > > root filesystem is RAID5 on /dev/md0, it comes back up cleanly - no > > reconstruction. > > Cool, isn't it! > > > > > Have we gotten a whole lot more enthusiastic about marking superblocks clean > > lately, or should I be worried? Obviously this always used to trigger > > reconstruction, until recently. > > Yes. Lots more enthusiastic. > If there is no write activity for 20msec, we mark the superblock clean > and write it out, and are careful to write out a dirty superblock > before allowing another write to complete.
Wow, thanks! That's really awesome, considering how long reconstruction takes this system (about an hour of completely useless otherwise).
-- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |