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. 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. -- 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 _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Prev by Date: ACPI breakage in 2.6.2-rc3 (and before)
- Next by Date: Re: PROBLEM: AES cryptoloop corruption under recent -mm kernels
- Previous by thread: Re: [RFC] killing the AMD53C974 and mac_NCR5380 drivers
- Next by thread: Re: RAID arrays not reconstructing in 2.6
- Indexes:[Main][Thread]