* RAID arrays not reconstructing in 2.6
@ 2004-02-01 17:15 Daniel Jacobowitz
2004-02-02 4:46 ` Neil Brown
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Jacobowitz @ 2004-02-01 17:15 UTC (permalink / raw)
To: linux-kernel; +Cc: neilb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RAID arrays not reconstructing in 2.6
2004-02-01 17:15 RAID arrays not reconstructing in 2.6 Daniel Jacobowitz
@ 2004-02-02 4:46 ` Neil Brown
2004-02-02 14:34 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Neil Brown @ 2004-02-02 4:46 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: linux-kernel
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.
NeilBrown
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RAID arrays not reconstructing in 2.6
2004-02-02 4:46 ` Neil Brown
@ 2004-02-02 14:34 ` Daniel Jacobowitz
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2004-02-02 14:34 UTC (permalink / raw)
To: Neil Brown; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-02-02 14:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-01 17:15 RAID arrays not reconstructing in 2.6 Daniel Jacobowitz
2004-02-02 4:46 ` Neil Brown
2004-02-02 14:34 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox