Re: 2.4.35.1 md problem

On Wed, Sep 05, 2007 at 03:45:45PM +0200, Beschorner Daniel wrote:
> I got a strange problem after I updated from 2.4.34.4 to 2.4.35.1:
> 
> The kernel raid autodetection assembles my 2 raid-1 arrays, but mdstat
> shows "0 blocks" for each md.
> So the filesystem check complains about no valid superblock, but the
> arrays seem to run fine.
> After raidstop/raidstart the blocks are displayed correctly and all is
> fine.
> But this is no solution, because the root fs is raid.
> 
> Could it be a compiler issue, I assume there is no change in raid since
> 2.4.34?!?
> 
> I use GCC 4.1.2 and no LVM.

Also, I forgot one important thing: could you please send me your .config ?

Thanks in advance,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • 2.4.35.1 md problem
    • From: "Beschorner Daniel" <[email protected]>

• Prev by Date: Re: [PATCH 2/2] Fix (improve) deadlock condition on module removal netfilter socket option removal
• Next by Date: Re: [PATCH] Fix preemptible lazy mode bug
• Previous by thread: 2.4.35.1 md problem
• Next by thread: [PATCH]: Stop bogus softlockup warnings in debug_show_all_locks (2nd try)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]