Re: [dm-devel] multipath and HSG80

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Make sure the kernel DM event model works (with "dmsetup wait")
If not, revert the Mike Christie patches from the udm patchset.

Ok... if i have understood...

i do
dmsetup -v wait volume1 0
and is sleeping...

sg_start /dev/sda 1
dmsetup wakes up and shows:

root@m2:/# dmsetup -v wait volume1 0
Name:              volume1
State:             ACTIVE
Tables present:    LIVE
Open count:        2
Event number:      1
Major, minor:      254, 0
Number of targets: 1

while kern.log shows:

Nov 26 12:44:56 m2 kernel: Device sdd not ready.
Nov 26 12:44:56 m2 kernel: end_request: I/O error, dev sdd, sector 27280

all right, the write operation continues its job...

now i do:
dmsetup -v wait volume1 1
and is sleeping...

sg_start /dev/sdd 1
dmsetup wakes up and shows:

root@m2:/# dmsetup -v wait volume1 1
Name:              volume1
State:             ACTIVE
Tables present:    LIVE
Open count:        2
Event number:      2
Major, minor:      254, 0
Number of targets: 1

while kern.log shows:
Message from syslogd@m2 at Fri Nov 26 12:47:21 2004 ...
m2 kernel: REISERFS: panic (device dm-0): journal-601, buffer write failed
Nov 26 12:47:21 m2 kernel: Device sda not ready.
Nov 26 12:47:21 m2 kernel: end_request: I/O error, dev sda, sector 23664
Nov 26 12:47:21 m2 kernel: Buffer I/O error on device dm-0, logical block 2958
Nov 26 12:47:21 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:47:21 m2 kernel: Buffer I/O error on device dm-0, logical block 2959
Nov 26 12:47:21 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:47:21 m2 kernel: Buffer I/O error on device dm-0, logical block 2960
Nov 26 12:47:21 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:47:21 m2 kernel: Buffer I/O error on device dm-0, logical block 2961
Nov 26 12:47:21 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:47:21 m2 kernel: REISERFS: panic (device dm-0): journal-601, buffer write failed

now the case when i emulate the controller failure:
on hsg80 console i do a restart other...

dmsetup wakes up showing:

root@m2:/# dmsetup -v wait volume 0
Name:              volume
State:             ACTIVE
Tables present:    LIVE
Open count:        2
Event number:      1
Major, minor:      254, 0
Number of targets: 1

while the kern.log shows:

Message from syslogd@m2 at Fri Nov 26 12:55:47 2004 ...
m2 kernel: REISERFS: panic (device dm-0): journal-601, buffer write failed
Nov 26 12:55:47 m2 kernel: Device sdd not ready.
Nov 26 12:55:47 m2 kernel: end_request: I/O error, dev sdd, sector 39208
Nov 26 12:55:47 m2 kernel: Device sda not ready.
Nov 26 12:55:47 m2 kernel: end_request: I/O error, dev sda, sector 39208
Nov 26 12:55:47 m2 kernel: Buffer I/O error on device dm-0, logical block 4901
Nov 26 12:55:47 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:55:47 m2 kernel: Buffer I/O error on device dm-0, logical block 4902
Nov 26 12:55:47 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:55:47 m2 kernel: Buffer I/O error on device dm-0, logical block 4903
Nov 26 12:55:47 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:55:47 m2 kernel: Buffer I/O error on device dm-0, logical block 4904
Nov 26 12:55:47 m2 kernel: lost page write due to I/O error on dm-0
Nov 26 12:55:47 m2 kernel: REISERFS: panic (device dm-0): journal-601, buffer write failed

wath's the next step?

thanks

Nicola Ranaldo

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux