Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over

2009-02-05 Thread John McMonagle

Neil Brown wrote:

On Wednesday February 4, madd...@debian.org wrote:
  

tags 510261 confirmed upstream
forwarded 510261 ne...@suse.de
thanks

also sprach John McMonagle jo...@advocap.org [2008.12.30.2214 +0100]:


In both cases I rebooted before the sync was done.
In both cases arrays re-synced from the beginning.
After it finished syncing a reboot does not cause a re-sync.
  

This is something Neil would need to fix in the kernel. I think
I remember there being some talk about that, but I may misremember.
There is nothing mdadm can do against that, I think.



No, this has nothing to do with mdadm.

But it should not behave like this, and in my experience it doesn't.

There was a bug related to this that was fixed in 2.6.25, but I'm
fairly sure lenny has a more recent kernel than that (??).

How exactly did you reboot?  Just shutdown now or /sbin/reboot or
turn power off or ...

Exactly what kernel is used during the install?

NeilBrown
  

Neil

Wish I could be sure but pretty sure  I used reboot command.
In the most recent case have 2 1-tb drives and recall it resyncing at 
least twice.


Looking at the installer logs. Did install  2008-12-15.
Installer syslog gives says 2.6.26-1-486  Changed to  2.6.26-1-686.

John

--
John McMonagle
IT Manager
Advocap Inc.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over

2009-02-04 Thread martin f krafft
tags 510261 confirmed upstream
forwarded 510261 ne...@suse.de
thanks

also sprach John McMonagle jo...@advocap.org [2008.12.30.2214 +0100]:
 In both cases I rebooted before the sync was done.
 In both cases arrays re-synced from the beginning.
 After it finished syncing a reboot does not cause a re-sync.

This is something Neil would need to fix in the kernel. I think
I remember there being some talk about that, but I may misremember.
There is nothing mdadm can do against that, I think.

-- 
 .''`.   martin f. krafft madd...@d.o  Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over

2009-02-04 Thread Neil Brown
On Wednesday February 4, madd...@debian.org wrote:
 tags 510261 confirmed upstream
 forwarded 510261 ne...@suse.de
 thanks
 
 also sprach John McMonagle jo...@advocap.org [2008.12.30.2214 +0100]:
  In both cases I rebooted before the sync was done.
  In both cases arrays re-synced from the beginning.
  After it finished syncing a reboot does not cause a re-sync.
 
 This is something Neil would need to fix in the kernel. I think
 I remember there being some talk about that, but I may misremember.
 There is nothing mdadm can do against that, I think.

No, this has nothing to do with mdadm.

But it should not behave like this, and in my experience it doesn't.

There was a bug related to this that was fixed in 2.6.25, but I'm
fairly sure lenny has a more recent kernel than that (??).

How exactly did you reboot?  Just shutdown now or /sbin/reboot or
turn power off or ...

Exactly what kernel is used during the install?

NeilBrown



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over

2008-12-30 Thread John McMonagle

Package: mdadm
Version: 2.6.7.1-1
Severity: normal

Did a couple raid1 installs of lenny lately.
This one amd64 another a 32 bit install.

In both cases I rebooted before the sync was done.
In both cases arrays re-synced from the beginning.
After it finished syncing a reboot does not cause a re-sync.

I did not touch any mdadm configuration files.

John

-- Package-specific info:
--- mount output
/dev/md0 on / type ext3 (rw,noatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/mapper/vg0-home on /home type xfs (rw,noatime)
/dev/mapper/vg0-tmp on /tmp type xfs (rw,noatime)
/dev/mapper/vg0-local on /usr/local type xfs (rw,noatime)
/dev/mapper/vg0-var on /var type xfs (rw,noatime)
/dev/mapper/vg0-work on /work type xfs (rw,noatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
server:/extra on /extra type nfs 
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/backup on /backup type nfs 
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/shared/main on /main type nfs 
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/home on /homejm type nfs 
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/video on /video type nfs4 
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,addr=192.168.101.1)
fondy:/home on /fondy type nfs4 
(rw,nodev,sync,proto=tcp,retry=10,rsize=32768,wsize=32768,hard,intr,addr=192.168.2.1)


--- mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST system

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=0d8df827:0de622b7:82658f7d:40808bc9
ARRAY /dev/md1 level=raid1 num-devices=2 
UUID=a575b291:eb792299:1d6cd8aa:0f2a4770


# This file was auto-generated on Fri, 19 Dec 2008 18:05:14 -0600
# by mkconf $Id$

--- /proc/mdstat:
Personalities : [raid1]
md1 : active raid1 sda2[0] sdb2[1]
  371173696 blocks [2/2] [UU]
  bitmap: 2/177 pages [8KB], 1024KB chunk

md0 : active raid1 sda1[0] sdb1[1]
  19534912 blocks [2/2] [UU]
  bitmap: 0/150 pages [0KB], 64KB chunk

unused devices: none

--- /proc/partitions:
major minor  #blocks  name

   8 0  488386584 sda
   8 1   19535008 sda1
   8 2  371189857 sda2
   8 3  1 sda3
   8 5   19535008 sda5
   816  390711384 sdb
   817   19535008 sdb1
   818  371173792 sdb2
   9 0   19534912 md0
   9 1  371173696 md1
 253 0   26214400 dm-0
 253 12097152 dm-1
 253 22097152 dm-2
 253 32097152 dm-3
 253 4   41943040 dm-4
 253 52097152 dm-5

--- initrd.img-2.6.26-1-amd64:
44415 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-mod.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-snapshot.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-log.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-mirror.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/md-mod.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/linear.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/multipath.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid0.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid1.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid456.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm

--- /proc/modules:
dm_mirror 20608 0 - Live 0xa0166000
dm_log 13956 1 dm_mirror, Live 0xa0161000
dm_snapshot 19400 0 - Live 0xa015b000
dm_mod 58864 16 dm_mirror,dm_log,dm_snapshot, Live 0xa014b000
raid1 24192 2 - Live 0xa0144000
md_mod 80164 3 raid1, Live 0xa012f000

--- volume detail:

--- /proc/cmdline
root=/dev/md0 ro single

--- grub:
module  /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro console=tty0
kernel  /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro quiet
kernel  /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro single
kernel  /boot/vmlinuz-2.6.26-1-amd64 root=/dev/md0 ro quiet
kernel  /boot/vmlinuz-2.6.26-1-amd64 root=/dev/md0 ro single
kernel  /boot/vmlinuz-2.6.27-9-generic root=/dev/md0 ro