SuSE8.2 root RAID1 reiserfs, always resyncing after boot
From: John W. Fuerst (j.fuerst_at_A1.net)
Date: 03/28/04
- Next message: ThunderKit: "Re: rset8019.exe"
- Previous message: Thomas Keller: "Re: Problem with glx extension on FC1"
- Next in thread: Walter Mautner: "Re: SuSE8.2 root RAID1 reiserfs, always resyncing after boot"
- Reply: Walter Mautner: "Re: SuSE8.2 root RAID1 reiserfs, always resyncing after boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Mar 2004 15:30:44 GMT
Hi,
How can I prevent the RAID1 for root from doing a resync with each boot?
Shouldn't the RAID be clean after a regular shutdown?
I also did a 'fsck' on /dev/md0 from the rescue system. But next time
after the system was shutdown, when /dev/md0 was the root device (rw),
it would resync again with the next boot.
/dev/md1 is perfectly fine and resyncs not too often.
Some advice, please.
The setup:
I have setup my system to boot with GRUB from a harddisk device and have
the root filesystem on a RAID1 device. /home is on another RAID1 device.
The two harddisks are on seperate controllers.
Everything works fine exept the fact that '/dev/md0' is resyncing
everytime after boot. Is this normal or can you show a way to avoid that.
Info about the configuraton:
SuSE8.2, kernel 2.4.20-4GB (compiled with reiserfs.o and raid1.0
builtin), raidtools V1.00.3-24
/etc/fstab:
/dev/md0 / reiserfs
/dev/hda3 /boot ext2
/dev/md1 /home reiserfs
/etc/raidtab:
# md device [dev 9, 0] /dev/md0 queried online
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hde2
raid-disk 0
device /dev/hda2
raid-disk 1
....
I built the RAID1 according the instructions in
'Software-RAID-HOWTO.html' in degraided mode and 'raidhotadd'(ed)
/dev/md0 /dev/hda2, which was configured as faulty device, when setting
everything up.
/var/log/boot.msg:
<6>md: considering hde2 ...
<6>md: adding hde2 ...
<6>md: adding hda2 ...
<6>md: created md0
<6>md: bind<hda2,1>
<6>md: bind<hde2,2>
<6>md: running: <hde2><hda2>
<6>md: hde2's event counter: 00000025
<6>md: hda2's event counter: 00000025
<3>md: md0: raid array is not clean -- starting background reconstruction
<6>md: RAID level 1 does not need chunksize! Continuing anyway.
<6>md0: max total readahead window set to 508k
<6>md0: 1 data-disks, max readahead per data-disk: 508k
<6>raid1: device hde2 operational as mirror 0
<6>raid1: device hda2 operational as mirror 1
<4>raid1: raid set md0 not clean; reconstructing mirrors
<6>raid1: raid set md0 active with 2 out of 2 mirrors
<6>md: updating md0 RAID superblock on device
<6>md: hde2 [events: 00000026]<6>(write) hde2's sb offset: 45865408
<6>md: syncing RAID array md0
<6>md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
<6>md: using maximum available idle IO bandwith (but not more than
100000 KB/sec
) for reconstruction.
<6>md: using 508k window, over a total of 45865408 blocks.
<6>md: hda2 [events: 00000026]<6>(write) hda2's sb offset: 45865472
<6> [events: 00000000]
<3>md: invalid raid superblock magic on md0
<4>md: md0 has invalid sb, not importing!
<4>md: no nested md device found
<6>md: ... autorun DONE.
- Next message: ThunderKit: "Re: rset8019.exe"
- Previous message: Thomas Keller: "Re: Problem with glx extension on FC1"
- Next in thread: Walter Mautner: "Re: SuSE8.2 root RAID1 reiserfs, always resyncing after boot"
- Reply: Walter Mautner: "Re: SuSE8.2 root RAID1 reiserfs, always resyncing after boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
