[ubuntu-uk] Crossover Linux - Free today only
Spotted this: http://www.omgubuntu.co.uk/2012/10/run-windows-apps-in-ubuntu-with-crossover-for-linux-free-for-today-only Thought people may be interested. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[Bug 460906] Re: disk/by-uuid/foo symlink points to snapshot rather than the origin
Possibly users should be warned in some prominent location that if they're mounting by UUID then leaving an LVM snapshot in place could result in that being mounted on reboot. Changing the UUID of the 'real' disk during live operation simply because it's been snapshotted sounds reasonably insane - there's a case to be made for that being somewhat immutable after boot. It might make more sense to filter via mapper and/or by-path (I'm using by-path in LVM's filter right now to sanely strain the multipath devices out from regular sd* devices) if you're expecting to have stale LVM snapshots around at boot time. A user-configurable choice might make for reasonable compromise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/460906 Title: disk/by-uuid/foo symlink points to snapshot rather than the origin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/460906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030667] [NEW] LVM2 regex exclusion filtering applies incorrectly in some cases
Public bug reported: lvm.conf: If I add a|.*| into the regex array for the filter, it ignores my 'sd[b-z]' exclusions and any other items (eg loop, ram) after the [b-z]. It seems to be an issue with the use of square brackets inside the regex in certain ways. Eg if I use the line: filter = [ a|.*|, r|.*| ] or filter = [ a|.*|, r|loop| ] Then this filters _everything_ in the first example, or just loop devices respectively... just as you would expect. However as soon as I use something like: filter = [ a|.*|, r|loop[0-9]| ] Then I don't get any filtering at all... except that defining _only_ the removal filters, per: filter = [ r|loop[0-9]| ] .. and other filters of that ilk DO work as expected -- so long as I remove the accept-all regex. Even this line works as expected: filter = [ a|.*|, r|sd.| ] -- Possibly since placing the the match-any-single-character (.) in there changes the behaviour. The filter currently in use works as expected and looks like: filter = [ r|sd[b-z]|, r|ram[0-9]+|, r|loop[0-9]+|, ] --- DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION=Ubuntu 10.04.3 LTS --- lvm2: Installed: 2.02.54-1ubuntu4.1 Candidate: 2.02.54-1ubuntu4.1 Version table: *** 2.02.54-1ubuntu4.1 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2.02.54-1ubuntu4 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030667 Title: LVM2 regex exclusion filtering applies incorrectly in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1030667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
The root cause was in fact the lvm.conf filter, but explicitly not for the reason you'd think. The issue is that if I added a|.*| into regex array, it was ignoring my 'sd[b-z]', loop and ram exclusions, both singly and in combination. It seems to be an obscure issue with the use of square brackets inside the regex in certain ways. Eg if I use the line: filter = [ a|.*|, r|.*| ] or filter = [ a|.*|, r|loop| ] Then this filters _everything_ in the first example, or just loop devices respectively... just as you would expect. However as soon as I use something like: filter = [ a|.*|, r|loop[0-9]| ] Then I don't get any filtering at all... except that defining _only_ the removal filters, per: filter = [ r|loop[0-9]+| ] .. and other filters of that ilk DO work as expected -- so long as I remove the accept-all regex. I'm not sure if this parsing behaviour is intended -- it could be to do with the way the array is encapsulated. Even this line works as expected: filter = [ a|.*|, r|sd.[b-z]| ] -- Possibly since placing the the match-any-single-character (.) in there changes the behaviour. The filter currently in use works as expected and looks like: filter = [ r|sd[b-z]|, r|ram[0-9]+|, r|loop[0-9]+|, ] After update-initramfs and reboot, I can successfully disable paths, and the failover works perfectly. Your insight is much appreciated, I would never have expected /dev/mapper/mpath0 to become aliased to a single disk target. I suspect that what has actually happened is that things were working perfectly for a time, but then broke upon a reboot of the server. Ie, due to the lack of filtering, LVM jumbled the detected volumes at boot time (due to the way /dev is traversed) such that mpath0 was actually pointing at a fixed location eg /dev/sdb rather than being multipathed as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
The root cause was in fact the lvm.conf filter, but explicitly not for the reason you'd think. The issue is that if I added a|.*| into regex array, it was ignoring my 'sd[b-z]', loop and ram exclusions, both singly and in combination. It seems to be an obscure issue with the use of square brackets inside the regex in certain ways. Eg if I use the line: filter = [ a|.*|, r|.*| ] or filter = [ a|.*|, r|loop| ] Then this filters _everything_ in the first example, or just loop devices respectively... just as you would expect. However as soon as I use something like: filter = [ a|.*|, r|loop[0-9]| ] Then I don't get any filtering at all... except that defining _only_ the removal filters, per: filter = [ r|loop[0-9]+| ] .. and other filters of that ilk DO work as expected -- so long as I remove the accept-all regex. I'm not sure if this parsing behaviour is intended -- it could be to do with the way the array is encapsulated. Even this line works as expected: filter = [ a|.*|, r|sd.[b-z]| ] -- Possibly since placing the the match-any-single-character (.) in there changes the behaviour. The filter currently in use works as expected and looks like: filter = [ r|sd[b-z]|, r|ram[0-9]+|, r|loop[0-9]+|, ] After update-initramfs and reboot, I can successfully disable paths, and the failover works perfectly. Your insight is much appreciated, I would never have expected /dev/mapper/mpath0 to become aliased to a single disk target. I suspect that what has actually happened is that things were working perfectly for a time, but then broke upon a reboot of the server. Ie, due to the lack of filtering, LVM jumbled the detected volumes at boot time (due to the way /dev is traversed) such that mpath0 was actually pointing at a fixed location eg /dev/sdb rather than being multipathed as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Output from before and after commands is attached. I'm pretty sure you're right about the LVM device filter; I figured that setting the scsi-timeout to 90 seconds (being way longer than the TUR path checker, which is scheduled every 20 seconds) should be enough to handle the device failover. It's as if dm-4 is using sdk (for example), but when this changes, either the journal is somehow stuck trying to update via the failed path, or dm-4 gets removed from the virtual device list because sdk is no longer there, instead of being reinstated with a new path. -- (Yes, dm-4 is where the xfs filesystem is (mpath0). The multipathed dm- entries are currently dm-5, dm-6 and dm-7.) root@hostname:/etc# multipath -ll | grep dm- mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V mpath1 (360060e80058a07008a07000e) dm-5 HITACHI ,OPEN-V mpath0 (360060e80058a07008a072417) dm-6 HITACHI ,OPEN-V root@hostname:/etc# pvscan PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] PV /dev/sda1VG rgrprod-proc03 lvm2 [135.97 GiB / 108.03 GiB free] Total: 4 [643.96 GiB] / in use: 4 [643.96 GiB] / in no VG: 0 [0 ] /dev/mapper/test2-lvol0 on /tmp/test2 type xfs (rw) /dev/mapper/test-lvol0 on /tmp/test type ext4 (rw) /dev/mapper/mvsan-san on /srv/mysql type xfs (rw) --- Interestingly, this is before failure: root@hostname:/etc# find /sys/devices -name *dm-* -print | grep -v virtual | sort -t '/' --key=13 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-0 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-1 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:2/block/sdm/holders/dm-2 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:1/block/sdl/holders/dm-3 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:0/block/sdk/holders/dm-4 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:1/block/sdc/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:1/block/sdf/holders/dm-5 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:1/block/sdi/holders/dm-5 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:1/block/sdl/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:0/block/sdb/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:0/block/sde/holders/dm-6 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:0/block/sdh/holders/dm-6 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:0/block/sdk/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:2/block/sdd/holders/dm-7 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:2/block/sdg/holders/dm-7 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:2/block/sdj/holders/dm-7 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:2/block/sdm/holders/dm-7 After failure, that same listing looks like: root@hostname:/etc# find /sys/devices -name *dm-* -print | grep -v virtual | sort -t '/' --key=13 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-0 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-1 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:1/block/sdc/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:1/block/sdf/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:0/block/sdb/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:0/block/sde/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:2/block/sdd/holders/dm-7 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:2/block/sdg/holders/dm-7 Which I suppose is to be expected - except I'm guessing that the dm-(2,3,4) devices shouldn't disappear - they should map to the new sdX paths via the physical devices /dev/mapper/mpath(0,1,2) ... or however that pathing failover is meant to work in LVM. ** Attachment added: before and after tests https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3233696/+files/240712_1445.tgz -- You received this bug
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Output from before and after commands is attached. I'm pretty sure you're right about the LVM device filter; I figured that setting the scsi-timeout to 90 seconds (being way longer than the TUR path checker, which is scheduled every 20 seconds) should be enough to handle the device failover. It's as if dm-4 is using sdk (for example), but when this changes, either the journal is somehow stuck trying to update via the failed path, or dm-4 gets removed from the virtual device list because sdk is no longer there, instead of being reinstated with a new path. -- (Yes, dm-4 is where the xfs filesystem is (mpath0). The multipathed dm- entries are currently dm-5, dm-6 and dm-7.) root@hostname:/etc# multipath -ll | grep dm- mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V mpath1 (360060e80058a07008a07000e) dm-5 HITACHI ,OPEN-V mpath0 (360060e80058a07008a072417) dm-6 HITACHI ,OPEN-V root@hostname:/etc# pvscan PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] PV /dev/sda1VG rgrprod-proc03 lvm2 [135.97 GiB / 108.03 GiB free] Total: 4 [643.96 GiB] / in use: 4 [643.96 GiB] / in no VG: 0 [0 ] /dev/mapper/test2-lvol0 on /tmp/test2 type xfs (rw) /dev/mapper/test-lvol0 on /tmp/test type ext4 (rw) /dev/mapper/mvsan-san on /srv/mysql type xfs (rw) --- Interestingly, this is before failure: root@hostname:/etc# find /sys/devices -name *dm-* -print | grep -v virtual | sort -t '/' --key=13 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-0 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-1 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:2/block/sdm/holders/dm-2 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:1/block/sdl/holders/dm-3 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:0/block/sdk/holders/dm-4 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:1/block/sdc/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:1/block/sdf/holders/dm-5 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:1/block/sdi/holders/dm-5 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:1/block/sdl/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:0/block/sdb/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:0/block/sde/holders/dm-6 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:0/block/sdh/holders/dm-6 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:0/block/sdk/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:2/block/sdd/holders/dm-7 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:2/block/sdg/holders/dm-7 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-0/target6:0:0/6:0:0:2/block/sdj/holders/dm-7 /sys/devices/pci:00/:00:09.0/:24:00.0/host6/rport-6:0-1/target6:0:1/6:0:1:2/block/sdm/holders/dm-7 After failure, that same listing looks like: root@hostname:/etc# find /sys/devices -name *dm-* -print | grep -v virtual | sort -t '/' --key=13 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-0 /sys/devices/pci:00/:00:1c.0/:01:00.0/host4/target4:2:0/4:2:0:0/block/sda/sda1/holders/dm-1 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:1/block/sdc/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:1/block/sdf/holders/dm-5 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:0/block/sdb/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:0/block/sde/holders/dm-6 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-0/target5:0:0/5:0:0:2/block/sdd/holders/dm-7 /sys/devices/pci:00/:00:07.0/:1f:00.0/host5/rport-5:0-1/target5:0:1/5:0:1:2/block/sdg/holders/dm-7 Which I suppose is to be expected - except I'm guessing that the dm-(2,3,4) devices shouldn't disappear - they should map to the new sdX paths via the physical devices /dev/mapper/mpath(0,1,2) ... or however that pathing failover is meant to work in LVM. ** Attachment added: before and after tests https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3233696/+files/240712_1445.tgz -- You received this bug
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
It looks like all the /dev/mapper/mpathX targets, and the remaining 'sd' unique paths (with one fabric disabled) were all readable after the path shutdown, but the underlying LVs were somehow still deactivated when the paths disappeared. root@hostname-03:/srv/mysql# dmesg snip [1039812.298161] I/O error in filesystem (dm-4) meta-data dev dm-4 block 0x1f414af0 (xlog_iodone) error 5 buf count 3072 [1039812.311419] xfs_force_shutdown(dm-4,0x2) called from line 1043 of file /build/buildd/linux-2.6.32/fs/xfs/xfs_log.c. Return address = 0xa0162516 [1039812.311433] Filesystem dm-4: Log I/O Error Detected. Shutting down filesystem: dm-4 [1039812.326038] Please umount the filesystem, and rectify the problem(s) root@hostname:/srv/mysql# ls -l ls: cannot open directory .: Input/output error root@hostname:/srv/mysql# lvs -o lv_attr /dev/test2/lvol0: read failed after 0 of 2048 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/mvsan/san: read failed after 0 of 2048 at 0: Input/output error Attr -wi-ao -wi-ao -wi-ao -wi-ao -wi-ao root@hostname:/srv/mysql# dd if=/dev/mapper/mpath mpath0 mpath1 mpath2 root@hostname:/srv/mysql# dd if=/dev/mapper/mpath0 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.0191405 s, 267 kB/s root@hostname:/srv/mysql# dd if=/dev/mapper/mpath1 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.00693051 s, 739 kB/s root@hostname:/srv/mysql# dd if=/dev/mapper/mpath2 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.00559024 s, 916 kB/s - root@hostname:/srv/mysql# ls -l /dev/sd* brw-rw 1 root disk 8, 0 2012-07-11 14:24 /dev/sda brw-rw 1 root disk 8, 1 2012-07-11 14:24 /dev/sda1 brw-rw 1 root disk 8, 16 2012-07-11 14:24 /dev/sdb brw-rw 1 root disk 8, 32 2012-07-11 14:24 /dev/sdc brw-rw 1 root disk 8, 48 2012-07-11 14:24 /dev/sdd brw-rw 1 root disk 8, 64 2012-07-11 14:24 /dev/sde brw-rw 1 root disk 8, 80 2012-07-11 14:24 /dev/sdf brw-rw 1 root disk 8, 96 2012-07-11 14:24 /dev/sdg root@hostname:/srv/mysql# dd if=/dev/sdb of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 5.0139e-05 s, 102 MB/s root@hostname:/srv/mysql# dd if=/dev/sdc of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.0726e-05 s, 126 MB/s root@hostname:/srv/mysql# dd if=/dev/sdd of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.0935e-05 s, 125 MB/s root@hostname:/srv/mysql# dd if=/dev/sde of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.2647e-05 s, 120 MB/s root@hostname:/srv/mysql# dd if=/dev/sdf of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.1718e-05 s, 123 MB/s root@hostname:/srv/mysql# dd if=/dev/sdg of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.3425e-05 s, 118 MB/s -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
It looks like all the /dev/mapper/mpathX targets, and the remaining 'sd' unique paths (with one fabric disabled) were all readable after the path shutdown, but the underlying LVs were somehow still deactivated when the paths disappeared. root@hostname-03:/srv/mysql# dmesg snip [1039812.298161] I/O error in filesystem (dm-4) meta-data dev dm-4 block 0x1f414af0 (xlog_iodone) error 5 buf count 3072 [1039812.311419] xfs_force_shutdown(dm-4,0x2) called from line 1043 of file /build/buildd/linux-2.6.32/fs/xfs/xfs_log.c. Return address = 0xa0162516 [1039812.311433] Filesystem dm-4: Log I/O Error Detected. Shutting down filesystem: dm-4 [1039812.326038] Please umount the filesystem, and rectify the problem(s) root@hostname:/srv/mysql# ls -l ls: cannot open directory .: Input/output error root@hostname:/srv/mysql# lvs -o lv_attr /dev/test2/lvol0: read failed after 0 of 2048 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/mvsan/san: read failed after 0 of 2048 at 0: Input/output error Attr -wi-ao -wi-ao -wi-ao -wi-ao -wi-ao root@hostname:/srv/mysql# dd if=/dev/mapper/mpath mpath0 mpath1 mpath2 root@hostname:/srv/mysql# dd if=/dev/mapper/mpath0 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.0191405 s, 267 kB/s root@hostname:/srv/mysql# dd if=/dev/mapper/mpath1 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.00693051 s, 739 kB/s root@hostname:/srv/mysql# dd if=/dev/mapper/mpath2 of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 0.00559024 s, 916 kB/s - root@hostname:/srv/mysql# ls -l /dev/sd* brw-rw 1 root disk 8, 0 2012-07-11 14:24 /dev/sda brw-rw 1 root disk 8, 1 2012-07-11 14:24 /dev/sda1 brw-rw 1 root disk 8, 16 2012-07-11 14:24 /dev/sdb brw-rw 1 root disk 8, 32 2012-07-11 14:24 /dev/sdc brw-rw 1 root disk 8, 48 2012-07-11 14:24 /dev/sdd brw-rw 1 root disk 8, 64 2012-07-11 14:24 /dev/sde brw-rw 1 root disk 8, 80 2012-07-11 14:24 /dev/sdf brw-rw 1 root disk 8, 96 2012-07-11 14:24 /dev/sdg root@hostname:/srv/mysql# dd if=/dev/sdb of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 5.0139e-05 s, 102 MB/s root@hostname:/srv/mysql# dd if=/dev/sdc of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.0726e-05 s, 126 MB/s root@hostname:/srv/mysql# dd if=/dev/sdd of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.0935e-05 s, 125 MB/s root@hostname:/srv/mysql# dd if=/dev/sde of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.2647e-05 s, 120 MB/s root@hostname:/srv/mysql# dd if=/dev/sdf of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.1718e-05 s, 123 MB/s root@hostname:/srv/mysql# dd if=/dev/sdg of=/dev/null count=10 10+0 records in 10+0 records out 5120 bytes (5.1 kB) copied, 4.3425e-05 s, 118 MB/s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
To date, the issue hasn't been observed on the two physical hosts we have running 10.04.1 LTS with the same multipath-tools version, which certainly raises a flag. They are being used as mission critical / production database servers so I'm scheduling a window in which we will be able to confirm whether or not it is manifesting on those hosts too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
To date, the issue hasn't been observed on the two physical hosts we have running 10.04.1 LTS with the same multipath-tools version, which certainly raises a flag. They are being used as mission critical / production database servers so I'm scheduling a window in which we will be able to confirm whether or not it is manifesting on those hosts too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment removed: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218020/+files/strace_mpathd.log ** Attachment added: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218069/+files/strace_mpathd.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
-- lvm.conf blacklist should be fine, searches /dev but filters all
/dev/sd.*
I'll attach those files momentarily.
I didn't see any kpartx processes running at all; there wasn't anything
in an uninterruptable sleep state ('D') either.
Listing all kernel and some additional processes here (removed stuff
like apache / php processes and certain publicly identifiable stuff
that's not relevant)
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1 0.6 0.0 23828 2064 ?Ss 14:59 0:04 /sbin/init
root 2 0.0 0.0 0 0 ?S14:59 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ?S14:59 0:00 [migration/0]
root 4 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/0]
root 6 0.0 0.0 0 0 ?S14:59 0:00 [migration/1]
root 7 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/1]
root 8 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/1]
root 9 0.0 0.0 0 0 ?S14:59 0:00 [migration/2]
root10 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/2]
root11 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/2]
root12 0.0 0.0 0 0 ?S14:59 0:00 [migration/3]
root13 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/3]
root14 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/3]
root15 0.0 0.0 0 0 ?S14:59 0:00 [migration/4]
root16 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/4]
root17 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/4]
root18 0.0 0.0 0 0 ?S14:59 0:00 [migration/5]
root19 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/5]
root20 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/5]
root21 0.0 0.0 0 0 ?S14:59 0:00 [migration/6]
root22 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/6]
root23 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/6]
root24 0.0 0.0 0 0 ?S14:59 0:00 [migration/7]
root25 0.1 0.0 0 0 ?S14:59 0:01 [ksoftirqd/7]
root26 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/7]
root27 0.0 0.0 0 0 ?S14:59 0:00 [migration/8]
root28 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/8]
root29 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/8]
root30 0.0 0.0 0 0 ?S14:59 0:00 [migration/9]
root31 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/9]
root32 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/9]
root33 0.0 0.0 0 0 ?S14:59 0:00 [migration/10]
root34 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/10]
root35 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/10]
root36 0.0 0.0 0 0 ?S14:59 0:00 [migration/11]
root37 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/11]
root38 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/11]
root39 0.0 0.0 0 0 ?S14:59 0:00 [migration/12]
root40 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/12]
root41 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/12]
root42 0.0 0.0 0 0 ?S14:59 0:00 [migration/13]
root43 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/13]
root44 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/13]
root45 0.0 0.0 0 0 ?S14:59 0:00 [migration/14]
root46 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/14]
root47 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/14]
root48 0.0 0.0 0 0 ?S14:59 0:00 [migration/15]
root49 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/15]
root50 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/15]
root51 0.0 0.0 0 0 ?S14:59 0:00 [migration/16]
root52 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/16]
root53 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/16]
root54 0.0 0.0 0 0 ?S14:59 0:00 [migration/17]
root55 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/17]
root56 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/17]
root57 0.0 0.0 0 0 ?S14:59 0:00 [migration/18]
root58 0.0 0.0
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Storage devices:
$ sudo lsscsi
[0:0:0:0]cd/dvd TSSTcorp CDDVDW TS-L633F IT03 /dev/sr0
[4:2:0:0]diskIBM ServeRAID M5015 2.12 /dev/sda
[5:0:0:0]diskHITACHI OPEN-V 6008 /dev/sdb
[5:0:0:1]diskHITACHI OPEN-V 6008 /dev/sdc
[5:0:0:2]diskHITACHI OPEN-V 6008 /dev/sdd
[5:0:1:0]diskHITACHI OPEN-V 6008 /dev/sde
[5:0:1:1]diskHITACHI OPEN-V 6008 /dev/sdf
[5:0:1:2]diskHITACHI OPEN-V 6008 /dev/sdg
[6:0:0:0]diskHITACHI OPEN-V 6008 /dev/sdh
[6:0:0:1]diskHITACHI OPEN-V 6008 /dev/sdi
[6:0:0:2]diskHITACHI OPEN-V 6008 /dev/sdj
[6:0:1:0]diskHITACHI OPEN-V 6008 /dev/sdk
[6:0:1:1]diskHITACHI OPEN-V 6008 /dev/sdl
[6:0:1:2]diskHITACHI OPEN-V 6008 /dev/sdm
Zoning:
- There are two HBAs. Each HBA is plugged into a separate Brocade DCX switch,
and each switch is connected to a different fabric (Fabric A and Fabric B
respectively)
- The storage array presenting the luns is also directly connected to the same
switches, in each Fabric via 4 ports (Array ports 1A,3A,6A,8A - Fabric A;
Ports 2A,4A,5A,8A - Fabric B).
- Each HBA is zoned so as to see two storage array ports (2 in each fabric).
Basically this means that when I disable the FC port an HBA is connected to, it
loses two paths to the lun.
HBA1 - DCX 1 (Fabric A) - 3A,6A
HBA2 - DCX 2 (Fabric B) - 4A,5A
Blacklisting:
Thanks for pointing this out - (note that I only added in the 'SMART'
vendor/product after the problem initially exhibited - in an effort to
remove the warning regarding a USB flash storage device that appeared in
the multipath -ll output. It _shouldn't_ be a factor).
Fixed now, initrd updated. Reboot/testing later today (likely in about
3 hours' time).
$ echo show config | sudo multipathd -k
multipathd show config
defaults {
user_friendly_names yes
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
wwid 3600605b0039afe20ff54052e7d38
device {
vendor SMART
product SMART
}
device {
vendor DGC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
}
blacklist_exceptions {
}
--snip
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1020436
Title:
Cannot read superblock after FC multipath failover
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
I note this segfault has appeared in dmesg on the last couple of boots. [ 304.214560] multipathd[3083]: segfault at a ip 7f5eb838798a sp 7fffb225ebb0 error 4 in libc-2.11.1.so[7f5eb831+17a000] After adjusting the blacklist, updating initrd and rebooting, the same behaviour is exhibited when I shut the active FC port: [ 429.234838] qla2xxx :24:00.0: LOOP DOWN detected (2 3 0). [ 459.165399] rport-6:0-1: blocked FC remote port time out: removing target and saving binding [ 459.165875] rport-6:0-0: blocked FC remote port time out: removing target and saving binding [ 459.166496] device-mapper: multipath: Failing path 8:112. [ 459.166573] device-mapper: multipath: Failing path 8:128. [ 459.166765] device-mapper: multipath: Failing path 8:144. [ 459.166831] device-mapper: multipath: Failing path 8:160. [ 459.166914] device-mapper: multipath: Failing path 8:176. [ 459.166965] device-mapper: multipath: Failing path 8:192. [ 459.219341] sd 6:0:1:0: [sdk] Synchronizing SCSI cache [ 459.219374] sd 6:0:1:0: [sdk] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.220728] device-mapper: multipath: Failing path 8:112. [ 459.299111] sd 6:0:1:1: [sdl] Synchronizing SCSI cache [ 459.299138] sd 6:0:1:1: [sdl] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.300305] device-mapper: multipath: Failing path 8:128. [ 459.378913] sd 6:0:1:2: [sdm] Synchronizing SCSI cache [ 459.378943] sd 6:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.381678] device-mapper: multipath: Failing path 8:144. [ 459.430852] sd 6:0:0:1: [sdi] Unhandled error code [ 459.430854] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.430857] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 7f ff 80 00 00 08 00 [ 459.430862] end_request: I/O error, dev sdi, sector 8388480 [ 459.431165] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431166] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431168] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 7f ff f0 00 00 08 00 [ 459.431173] end_request: I/O error, dev sdi, sector 8388592 [ 459.431473] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431475] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431477] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.431482] end_request: I/O error, dev sdi, sector 0 [ 459.431767] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431770] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431772] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 08 00 00 08 00 [ 459.431776] end_request: I/O error, dev sdi, sector 8 [ 459.432072] sd 6:0:0:1: [sdi] Unhandled error code [ 459.432073] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432075] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.432081] end_request: I/O error, dev sdi, sector 0 [ 459.432397] sd 6:0:0:2: [sdj] Unhandled error code [ 459.432399] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432401] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 7f ff 80 00 00 08 00 [ 459.432406] end_request: I/O error, dev sdj, sector 8388480 [ 459.432712] sd 6:0:0:2: [sdj] Unhandled error code [ 459.432714] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432717] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 7f ff f0 00 00 08 00 [ 459.432723] end_request: I/O error, dev sdj, sector 8388592 [ 459.433034] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433036] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433039] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.433045] end_request: I/O error, dev sdj, sector 0 [ 459.433345] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433347] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433350] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 08 00 00 08 00 [ 459.433356] end_request: I/O error, dev sdj, sector 8 [ 459.433672] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433674] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433677] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.433684] end_request: I/O error, dev sdj, sector 0 [ 459.456208] sd 6:0:0:0: [sdh] Synchronizing SCSI cache [ 459.456236] sd 6:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.465583] sd 6:0:0:2: [sdj] Unhandled error code [ 459.465585] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.465588] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.465593] end_request: I/O error, dev sdj, sector 0 [ 459.548504] sd 6:0:0:1: [sdi] Synchronizing SCSI cache [ 459.548540] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.625817] sd 6:0:0:2: [sdj] Synchronizing SCSI cache [
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: strace_mpathd_110712.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219323/+files/strace_mpathd_110712.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: multipathd_stdout_110712.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219324/+files/multipathd_stdout_110712.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment removed: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218020/+files/strace_mpathd.log ** Attachment added: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218069/+files/strace_mpathd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Storage devices:
$ sudo lsscsi
[0:0:0:0]cd/dvd TSSTcorp CDDVDW TS-L633F IT03 /dev/sr0
[4:2:0:0]diskIBM ServeRAID M5015 2.12 /dev/sda
[5:0:0:0]diskHITACHI OPEN-V 6008 /dev/sdb
[5:0:0:1]diskHITACHI OPEN-V 6008 /dev/sdc
[5:0:0:2]diskHITACHI OPEN-V 6008 /dev/sdd
[5:0:1:0]diskHITACHI OPEN-V 6008 /dev/sde
[5:0:1:1]diskHITACHI OPEN-V 6008 /dev/sdf
[5:0:1:2]diskHITACHI OPEN-V 6008 /dev/sdg
[6:0:0:0]diskHITACHI OPEN-V 6008 /dev/sdh
[6:0:0:1]diskHITACHI OPEN-V 6008 /dev/sdi
[6:0:0:2]diskHITACHI OPEN-V 6008 /dev/sdj
[6:0:1:0]diskHITACHI OPEN-V 6008 /dev/sdk
[6:0:1:1]diskHITACHI OPEN-V 6008 /dev/sdl
[6:0:1:2]diskHITACHI OPEN-V 6008 /dev/sdm
Zoning:
- There are two HBAs. Each HBA is plugged into a separate Brocade DCX switch,
and each switch is connected to a different fabric (Fabric A and Fabric B
respectively)
- The storage array presenting the luns is also directly connected to the same
switches, in each Fabric via 4 ports (Array ports 1A,3A,6A,8A - Fabric A;
Ports 2A,4A,5A,8A - Fabric B).
- Each HBA is zoned so as to see two storage array ports (2 in each fabric).
Basically this means that when I disable the FC port an HBA is connected to, it
loses two paths to the lun.
HBA1 - DCX 1 (Fabric A) - 3A,6A
HBA2 - DCX 2 (Fabric B) - 4A,5A
Blacklisting:
Thanks for pointing this out - (note that I only added in the 'SMART'
vendor/product after the problem initially exhibited - in an effort to
remove the warning regarding a USB flash storage device that appeared in
the multipath -ll output. It _shouldn't_ be a factor).
Fixed now, initrd updated. Reboot/testing later today (likely in about
3 hours' time).
$ echo show config | sudo multipathd -k
multipathd show config
defaults {
user_friendly_names yes
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
wwid 3600605b0039afe20ff54052e7d38
device {
vendor SMART
product SMART
}
device {
vendor DGC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
}
blacklist_exceptions {
}
--snip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020436
Title:
Cannot read superblock after FC multipath failover
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
I note this segfault has appeared in dmesg on the last couple of boots. [ 304.214560] multipathd[3083]: segfault at a ip 7f5eb838798a sp 7fffb225ebb0 error 4 in libc-2.11.1.so[7f5eb831+17a000] After adjusting the blacklist, updating initrd and rebooting, the same behaviour is exhibited when I shut the active FC port: [ 429.234838] qla2xxx :24:00.0: LOOP DOWN detected (2 3 0). [ 459.165399] rport-6:0-1: blocked FC remote port time out: removing target and saving binding [ 459.165875] rport-6:0-0: blocked FC remote port time out: removing target and saving binding [ 459.166496] device-mapper: multipath: Failing path 8:112. [ 459.166573] device-mapper: multipath: Failing path 8:128. [ 459.166765] device-mapper: multipath: Failing path 8:144. [ 459.166831] device-mapper: multipath: Failing path 8:160. [ 459.166914] device-mapper: multipath: Failing path 8:176. [ 459.166965] device-mapper: multipath: Failing path 8:192. [ 459.219341] sd 6:0:1:0: [sdk] Synchronizing SCSI cache [ 459.219374] sd 6:0:1:0: [sdk] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.220728] device-mapper: multipath: Failing path 8:112. [ 459.299111] sd 6:0:1:1: [sdl] Synchronizing SCSI cache [ 459.299138] sd 6:0:1:1: [sdl] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.300305] device-mapper: multipath: Failing path 8:128. [ 459.378913] sd 6:0:1:2: [sdm] Synchronizing SCSI cache [ 459.378943] sd 6:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.381678] device-mapper: multipath: Failing path 8:144. [ 459.430852] sd 6:0:0:1: [sdi] Unhandled error code [ 459.430854] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.430857] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 7f ff 80 00 00 08 00 [ 459.430862] end_request: I/O error, dev sdi, sector 8388480 [ 459.431165] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431166] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431168] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 7f ff f0 00 00 08 00 [ 459.431173] end_request: I/O error, dev sdi, sector 8388592 [ 459.431473] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431475] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431477] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.431482] end_request: I/O error, dev sdi, sector 0 [ 459.431767] sd 6:0:0:1: [sdi] Unhandled error code [ 459.431770] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.431772] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 08 00 00 08 00 [ 459.431776] end_request: I/O error, dev sdi, sector 8 [ 459.432072] sd 6:0:0:1: [sdi] Unhandled error code [ 459.432073] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432075] sd 6:0:0:1: [sdi] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.432081] end_request: I/O error, dev sdi, sector 0 [ 459.432397] sd 6:0:0:2: [sdj] Unhandled error code [ 459.432399] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432401] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 7f ff 80 00 00 08 00 [ 459.432406] end_request: I/O error, dev sdj, sector 8388480 [ 459.432712] sd 6:0:0:2: [sdj] Unhandled error code [ 459.432714] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.432717] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 7f ff f0 00 00 08 00 [ 459.432723] end_request: I/O error, dev sdj, sector 8388592 [ 459.433034] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433036] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433039] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.433045] end_request: I/O error, dev sdj, sector 0 [ 459.433345] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433347] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433350] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 08 00 00 08 00 [ 459.433356] end_request: I/O error, dev sdj, sector 8 [ 459.433672] sd 6:0:0:2: [sdj] Unhandled error code [ 459.433674] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.433677] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.433684] end_request: I/O error, dev sdj, sector 0 [ 459.456208] sd 6:0:0:0: [sdh] Synchronizing SCSI cache [ 459.456236] sd 6:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.465583] sd 6:0:0:2: [sdj] Unhandled error code [ 459.465585] sd 6:0:0:2: [sdj] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.465588] sd 6:0:0:2: [sdj] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [ 459.465593] end_request: I/O error, dev sdj, sector 0 [ 459.548504] sd 6:0:0:1: [sdi] Synchronizing SCSI cache [ 459.548540] sd 6:0:0:1: [sdi] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 459.625817] sd 6:0:0:2: [sdj] Synchronizing SCSI cache [
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: strace_mpathd_110712.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219323/+files/strace_mpathd_110712.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: multipathd_stdout_110712.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219324/+files/multipathd_stdout_110712.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Hi Peter, Thanks for picking this up. Note: I ran an 'update-initramfs -u -k all' and rebooted just for good measure before proceeding. There's some output regarding a missing firmware file, I'm not sure it's relevant: root@rgrprod-pmdh-proc-03:/etc# update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-2.6.32-41-server W: Possible missing firmware /lib/firmware/ql8100_fw.bin for module qla2xxx Oddly, multipathd didn't log a single thing to stderr. ** Attachment added: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218020/+files/strace_mpathd.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
note: multipath_stderr.log exists, but is empty. ** Attachment added: multipathd_stdout.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218021/+files/multipathd_stdout.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
user@hostname:~$ sudo dmsetup table
mpath2: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:48
1000 8:96 1000 8:144 1000 8:192 1000
mpath1: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:128
1000 8:32 1000 8:80 1000 8:176 1000
mpath0: 0 1048576000 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:160
1000 8:16 1000 8:64 1000 8:112 1000
test2-lvol0: 0 8380416 linear 8:192 384
test-lvol0: 0 8380416 linear 8:176 384
vgname2-san: 0 1048567808 linear 8:160 384
vgname-slash: 0 48824320 linear 8:1 384
vgname-swap: 0 9764864 linear 8:1 48824704
user@hostname:~$ sudo echo show config | sudo multipathd -k
multipathd show config
defaults {
user_friendly_names yes
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
wwid 3600605b0039afe20ff54052e7d38
device {
vendor DGC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
}
blacklist_exceptions {
}
devices {
device {
vendor APPLE*
product Xserve RAID
path_grouping_policy multibus
}
device {
vendor 3PARdata
product VV
path_grouping_policy multibus
}
device {
vendor DEC
product HSG80
path_grouping_policy group_by_prio
path_checker hp_sw
features 1 queue_if_no_path
hardware_handler 1 hp_sw
prio_callout /sbin/mpath_prio_hp_sw /dev/%n
}
device {
vendor HP
product A6189A
path_grouping_policy multibus
path_checker readsector0
}
device {
vendor (COMPAQ|HP)
product (MSA|HSV)1.0.*
path_grouping_policy group_by_prio
path_checker hp_sw
features 1 queue_if_no_path
hardware_handler 1 hp_sw
prio_callout /sbin/mpath_prio_hp_sw /dev/%n
}
device {
vendor HP
product MSA VOLUME
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor (COMPAQ|HP)
product (MSA|HSV)1.1.*
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor HP
product HSV2.*
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor HP
product LOGICAL VOLUME.*
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id -n -g -u -d /dev/%n
path_checker tur
}
device {
vendor DDN
product SAN DataDirector
path_grouping_policy multibus
}
device {
vendor EMC
product SYMMETRIX
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id -g -u -ppre-spc3-83 -d /dev/%n
path_checker readsector0
}
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
path_checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 emc
prio_callout /sbin/mpath_prio_emc /dev/%n
failback immediate
no_path_retry 60
}
device {
vendor FSC
product CentricStor
path_grouping_policy group_by_serial
path_checker readsector0
}
device {
vendor (HITACHI|HP)
product OPEN-.*
path_grouping_policy multibus
path_checker tur
features 1 queue_if_no_path
}
device {
vendor HITACHI
product DF.*
path_grouping_policy group_by_prio
path_checker tur
features 1 queue_if_no_path
prio_callout /sbin/mpath_prio_hds_modular /dev/%n
failback immediate
}
device {
vendor IBM
product ProFibre 4000R
path_grouping_policy multibus
path_checker readsector0
}
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: multipath.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218022/+files/multipath.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: lvm.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218023/+files/lvm.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
note: /dev/sda is a raid volume used for the root vg; the filter is actually r|/dev/sd[b-z]| -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
Hi Peter, Thanks for picking this up. Note: I ran an 'update-initramfs -u -k all' and rebooted just for good measure before proceeding. There's some output regarding a missing firmware file, I'm not sure it's relevant: root@rgrprod-pmdh-proc-03:/etc# update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-2.6.32-41-server W: Possible missing firmware /lib/firmware/ql8100_fw.bin for module qla2xxx Oddly, multipathd didn't log a single thing to stderr. ** Attachment added: strace_mpathd.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218020/+files/strace_mpathd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
note: multipath_stderr.log exists, but is empty. ** Attachment added: multipathd_stdout.log https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218021/+files/multipathd_stdout.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
user@hostname:~$ sudo dmsetup table
mpath2: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:48
1000 8:96 1000 8:144 1000 8:192 1000
mpath1: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:128
1000 8:32 1000 8:80 1000 8:176 1000
mpath0: 0 1048576000 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:160
1000 8:16 1000 8:64 1000 8:112 1000
test2-lvol0: 0 8380416 linear 8:192 384
test-lvol0: 0 8380416 linear 8:176 384
vgname2-san: 0 1048567808 linear 8:160 384
vgname-slash: 0 48824320 linear 8:1 384
vgname-swap: 0 9764864 linear 8:1 48824704
user@hostname:~$ sudo echo show config | sudo multipathd -k
multipathd show config
defaults {
user_friendly_names yes
}
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^dcssblk[0-9]*
devnode ^cciss!c[0-9]d[0-9]*
wwid 3600605b0039afe20ff54052e7d38
device {
vendor DGC
product LUNZ
}
device {
vendor IBM
product S/390.*
}
}
blacklist_exceptions {
}
devices {
device {
vendor APPLE*
product Xserve RAID
path_grouping_policy multibus
}
device {
vendor 3PARdata
product VV
path_grouping_policy multibus
}
device {
vendor DEC
product HSG80
path_grouping_policy group_by_prio
path_checker hp_sw
features 1 queue_if_no_path
hardware_handler 1 hp_sw
prio_callout /sbin/mpath_prio_hp_sw /dev/%n
}
device {
vendor HP
product A6189A
path_grouping_policy multibus
path_checker readsector0
}
device {
vendor (COMPAQ|HP)
product (MSA|HSV)1.0.*
path_grouping_policy group_by_prio
path_checker hp_sw
features 1 queue_if_no_path
hardware_handler 1 hp_sw
prio_callout /sbin/mpath_prio_hp_sw /dev/%n
}
device {
vendor HP
product MSA VOLUME
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor (COMPAQ|HP)
product (MSA|HSV)1.1.*
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor HP
product HSV2.*
path_grouping_policy group_by_prio
path_checker tur
prio_callout /sbin/mpath_prio_alua /dev/%n
failback immediate
}
device {
vendor HP
product LOGICAL VOLUME.*
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id -n -g -u -d /dev/%n
path_checker tur
}
device {
vendor DDN
product SAN DataDirector
path_grouping_policy multibus
}
device {
vendor EMC
product SYMMETRIX
path_grouping_policy multibus
getuid_callout /lib/udev/scsi_id -g -u -ppre-spc3-83 -d /dev/%n
path_checker readsector0
}
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
path_checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 emc
prio_callout /sbin/mpath_prio_emc /dev/%n
failback immediate
no_path_retry 60
}
device {
vendor FSC
product CentricStor
path_grouping_policy group_by_serial
path_checker readsector0
}
device {
vendor (HITACHI|HP)
product OPEN-.*
path_grouping_policy multibus
path_checker tur
features 1 queue_if_no_path
}
device {
vendor HITACHI
product DF.*
path_grouping_policy group_by_prio
path_checker tur
features 1 queue_if_no_path
prio_callout /sbin/mpath_prio_hds_modular /dev/%n
failback immediate
}
device {
vendor IBM
product ProFibre 4000R
path_grouping_policy multibus
path_checker readsector0
}
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
-- lvm.conf blacklist should be fine, searches /dev but filters all
/dev/sd.*
I'll attach those files momentarily.
I didn't see any kpartx processes running at all; there wasn't anything
in an uninterruptable sleep state ('D') either.
Listing all kernel and some additional processes here (removed stuff
like apache / php processes and certain publicly identifiable stuff
that's not relevant)
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1 0.6 0.0 23828 2064 ?Ss 14:59 0:04 /sbin/init
root 2 0.0 0.0 0 0 ?S14:59 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ?S14:59 0:00 [migration/0]
root 4 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/0]
root 6 0.0 0.0 0 0 ?S14:59 0:00 [migration/1]
root 7 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/1]
root 8 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/1]
root 9 0.0 0.0 0 0 ?S14:59 0:00 [migration/2]
root10 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/2]
root11 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/2]
root12 0.0 0.0 0 0 ?S14:59 0:00 [migration/3]
root13 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/3]
root14 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/3]
root15 0.0 0.0 0 0 ?S14:59 0:00 [migration/4]
root16 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/4]
root17 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/4]
root18 0.0 0.0 0 0 ?S14:59 0:00 [migration/5]
root19 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/5]
root20 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/5]
root21 0.0 0.0 0 0 ?S14:59 0:00 [migration/6]
root22 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/6]
root23 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/6]
root24 0.0 0.0 0 0 ?S14:59 0:00 [migration/7]
root25 0.1 0.0 0 0 ?S14:59 0:01 [ksoftirqd/7]
root26 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/7]
root27 0.0 0.0 0 0 ?S14:59 0:00 [migration/8]
root28 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/8]
root29 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/8]
root30 0.0 0.0 0 0 ?S14:59 0:00 [migration/9]
root31 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/9]
root32 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/9]
root33 0.0 0.0 0 0 ?S14:59 0:00 [migration/10]
root34 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/10]
root35 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/10]
root36 0.0 0.0 0 0 ?S14:59 0:00 [migration/11]
root37 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/11]
root38 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/11]
root39 0.0 0.0 0 0 ?S14:59 0:00 [migration/12]
root40 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/12]
root41 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/12]
root42 0.0 0.0 0 0 ?S14:59 0:00 [migration/13]
root43 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/13]
root44 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/13]
root45 0.0 0.0 0 0 ?S14:59 0:00 [migration/14]
root46 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/14]
root47 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/14]
root48 0.0 0.0 0 0 ?S14:59 0:00 [migration/15]
root49 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/15]
root50 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/15]
root51 0.0 0.0 0 0 ?S14:59 0:00 [migration/16]
root52 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/16]
root53 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/16]
root54 0.0 0.0 0 0 ?S14:59 0:00 [migration/17]
root55 0.0 0.0 0 0 ?S14:59 0:00 [ksoftirqd/17]
root56 0.0 0.0 0 0 ?S14:59 0:00 [watchdog/17]
root57 0.0 0.0 0 0 ?S14:59 0:00 [migration/18]
root58 0.0 0.0
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: multipath.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218022/+files/multipath.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
** Attachment added: lvm.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218023/+files/lvm.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after FC multipath failover
note: /dev/sda is a raid volume used for the root vg; the filter is actually r|/dev/sd[b-z]| -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] Re: Cannot read superblock after fibre path failover
** Summary changed: - Multiple filesystems cannot read superblock after fibre path failover + Cannot read superblock after fibre path failover ** Summary changed: - Cannot read superblock after fibre path failover + Cannot read superblock after FC multipath failover -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1020436] Re: Cannot read superblock after fibre path failover
** Summary changed: - Multiple filesystems cannot read superblock after fibre path failover + Cannot read superblock after fibre path failover ** Summary changed: - Cannot read superblock after fibre path failover + Cannot read superblock after FC multipath failover -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020436] [NEW] Multiple filesystems cannot read superblock after fibre path failover
Public bug reported: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@host:~# lsb_release -rd Description:Ubuntu 10.04.3 LTS Release:10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@host:~# lvscan /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@host:~# pvscan /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@host:~# multipath -ll mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:2 sdd 8:48 [active][ready] \_ 6:0:1:2 sdg 8:96 [active][ready] \_ 7:0:0:2 sdj 8:144 [active][ready] \_ 7:0:1:2 sdp 8:240 [active][ready] mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:1 sdc 8:32 [active][ready] \_ 6:0:1:1 sdf 8:80 [active][ready] \_ 7:0:0:1 sdi 8:128 [active][ready] \_ 7:0:1:1 sdo 8:224 [active][ready] mpath0 (360060e80058a07008a072417) dm-5 HITACHI ,OPEN-V [size=500G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:0 sdb 8:16 [active][ready] \_ 6:0:1:0 sde 8:64 [active][ready] \_ 7:0:0:0 sdh 8:112 [active][ready] \_ 7:0:1:0 sdk 8:160 [active][ready] The dmesg output is very instructive, but still doesn't help with the root cause per se. I set the scsi-timeouts nice and high (90 seconds) to accommodate any potential delays in path failover. The path checks (test unit ready/TUR) occur about every 20 seconds. See below: [ 2192.891962] qla2xxx :24:00.0: LOOP DOWN detected (2 3 0). [ .820850] rport-7:0-0: blocked FC remote port time out: removing target and saving binding [ .821297] rport-7:0-1: blocked FC remote port time out: removing target and saving binding [ .827286] device-mapper: multipath: Failing path 8:112. [ .827369] device-mapper: multipath: Failing path 8:160. So this is all as expected. Then: [ .924665] sd 7:0:0:0: [sdh] Synchronizing SCSI cache [ .924696] sd 7:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .926071] device-mapper: multipath: Failing path 8:160. [ .976444] sd 7:0:1:2: [sdm] Unhandled error code [ .976446] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .976449] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 00 00 00 01 00 [ .976455] end_request: I/O error, dev sdm, sector 8380672 [ .980258] sd 7:0:1:2: [sdm] Unhandled error code [ .980260] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .980262] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 70 00 00 01 00 [ .980267] end_request: I/O error, dev sdm, sector 8380784 [ .984139] sd 7:0:1:2: [sdm]
[Bug 1020436] Re: Multiple filesystems cannot read superblock after fibre path failover
** Description changed: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@host:~# lsb_release -rd Description: Ubuntu 10.04.3 LTS Release: 10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@host:~# lvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@host:~# pvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] + /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@host:~# multipath -ll - mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V + mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:2 sdd 8:48 [active][ready] - \_ 6:0:1:2 sdg 8:96 [active][ready] - \_ 7:0:0:2 sdj 8:144 [active][ready] - \_ 7:0:1:2 sdp 8:240 [active][ready] - mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V + \_ 6:0:0:2 sdd 8:48 [active][ready] + \_ 6:0:1:2 sdg 8:96 [active][ready] + \_ 7:0:0:2 sdj 8:144 [active][ready] + \_ 7:0:1:2 sdp 8:240 [active][ready] + mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:1 sdc 8:32 [active][ready] - \_ 6:0:1:1 sdf 8:80 [active][ready] - \_ 7:0:0:1 sdi 8:128 [active][ready] - \_ 7:0:1:1 sdo 8:224 [active][ready] - mpath0
[Bug 1020436] [NEW] Multiple filesystems cannot read superblock after fibre path failover
Public bug reported: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@host:~# lsb_release -rd Description:Ubuntu 10.04.3 LTS Release:10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@host:~# lvscan /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@host:~# pvscan /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@host:~# multipath -ll mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:2 sdd 8:48 [active][ready] \_ 6:0:1:2 sdg 8:96 [active][ready] \_ 7:0:0:2 sdj 8:144 [active][ready] \_ 7:0:1:2 sdp 8:240 [active][ready] mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:1 sdc 8:32 [active][ready] \_ 6:0:1:1 sdf 8:80 [active][ready] \_ 7:0:0:1 sdi 8:128 [active][ready] \_ 7:0:1:1 sdo 8:224 [active][ready] mpath0 (360060e80058a07008a072417) dm-5 HITACHI ,OPEN-V [size=500G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:0 sdb 8:16 [active][ready] \_ 6:0:1:0 sde 8:64 [active][ready] \_ 7:0:0:0 sdh 8:112 [active][ready] \_ 7:0:1:0 sdk 8:160 [active][ready] The dmesg output is very instructive, but still doesn't help with the root cause per se. I set the scsi-timeouts nice and high (90 seconds) to accommodate any potential delays in path failover. The path checks (test unit ready/TUR) occur about every 20 seconds. See below: [ 2192.891962] qla2xxx :24:00.0: LOOP DOWN detected (2 3 0). [ .820850] rport-7:0-0: blocked FC remote port time out: removing target and saving binding [ .821297] rport-7:0-1: blocked FC remote port time out: removing target and saving binding [ .827286] device-mapper: multipath: Failing path 8:112. [ .827369] device-mapper: multipath: Failing path 8:160. So this is all as expected. Then: [ .924665] sd 7:0:0:0: [sdh] Synchronizing SCSI cache [ .924696] sd 7:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .926071] device-mapper: multipath: Failing path 8:160. [ .976444] sd 7:0:1:2: [sdm] Unhandled error code [ .976446] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .976449] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 00 00 00 01 00 [ .976455] end_request: I/O error, dev sdm, sector 8380672 [ .980258] sd 7:0:1:2: [sdm] Unhandled error code [ .980260] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .980262] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 70 00 00 01 00 [ .980267] end_request: I/O error, dev sdm, sector 8380784 [ .984139] sd 7:0:1:2: [sdm]
[Bug 1020436] Re: Multiple filesystems cannot read superblock after fibre path failover
** Description changed: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@host:~# lsb_release -rd Description: Ubuntu 10.04.3 LTS Release: 10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@host:~# lvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@host:~# pvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] + /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@host:~# multipath -ll - mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V + mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:2 sdd 8:48 [active][ready] - \_ 6:0:1:2 sdg 8:96 [active][ready] - \_ 7:0:0:2 sdj 8:144 [active][ready] - \_ 7:0:1:2 sdp 8:240 [active][ready] - mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V + \_ 6:0:0:2 sdd 8:48 [active][ready] + \_ 6:0:1:2 sdg 8:96 [active][ready] + \_ 7:0:0:2 sdj 8:144 [active][ready] + \_ 7:0:1:2 sdp 8:240 [active][ready] + mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:1 sdc 8:32 [active][ready] - \_ 6:0:1:1 sdf 8:80 [active][ready] - \_ 7:0:0:1 sdi 8:128 [active][ready] - \_ 7:0:1:1 sdo 8:224 [active][ready] - mpath0
Re: [ubuntu-uk] Precise - some thoughts .....
It is really easy to get basic hardware info for a Windows PC, IIRC right click my computer, then properities and it is in one of the tabs. Will reboot into WIn7 an check/confirm. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] STELLARIUM
Bump left side of screen (bottom) location config is at the top. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Shut down button missing on upgrade
Press alt-f2 gnome-sessions-daemon or in terminal gnome-sessions-daemon (no quotes). Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] Wubi and BCD store
Hi
Have posted about this on the main forum and been pointed towards a BCD
stores problem.
I have a Dell Inspiron N5010 with:
/dev/sda12048 206847 102400 de Dell Utility
/dev/sda2 * 2068482068684710247 HPFS/NTFS/exFAT
/dev/sda320686848 14356684761447 HPFS/NTFS/exFAT
/dev/sda4 143568894 976771071 416601089f W95 Ext'd (LBA)
/dev/sda5 143568896 356144984 106288044+ 7 HPFS/NTFS/exFAT
/dev/sda6 356145152 45380198348828416 83 Linux
/dev/sda7 453804032 469426175 7811072 82 Linux swap / Solaris
/dev/sda8 469428224 938178223 234375000 83 Linux
/dev/sda9 938178560 97677107119296256b W95 FAT32
sda3 = win7
sda6 = Debian Sid
I assume the problem is /dev/sda2 appears to be the boot drive (the *?
from fdisk above?).
I installed wubi on win7 but on reboot I am not seeing the menu to continue
install. Apparently I have two bcd stores on sda2 and 3.
More info:
sudo blkid
/dev/sda1: SEC_TYPE=msdos LABEL=DELLUTILITY UUID=3030-3030
TYPE=vfat
/dev/sda2: LABEL=Recovery UUID=CC70378A703779F2 TYPE=ntfs
/dev/sda3: LABEL=OS UUID=AC7C4EC27C4E86D4 TYPE=ntfs
/dev/sda5: LABEL=DATA UUID=C0FC8C15FC8C083C TYPE=ntfs
/dev/sda7: UUID=8e2d21af-a740-435d-aaed-98b84f49d490 TYPE=swap
/dev/sda9: UUID=CB53-547A TYPE=vfat
/dev/sda6: UUID=c94c4f87-5a16-4858-a57c-a71c98fe9eaf TYPE=ext4
/dev/sda8: UUID=2d495018-5697-4af7-9c69-dc23e41c2d50 TYPE=ext4
C:\Users\Stevebcdedit
Windows Boot Manager
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject{6abef735-3411-11de-8ea8-ac010edf8f1e}
displayorder{current}
{503bf9ab-30c8-11e1-9d62-08002700a8c7}
bootsequence{503bf9ab-30c8-11e1-9d62-08002700a8c7}
toolsdisplayorder {memdiag}
timeout 10
displaybootmenu Yes
Windows Boot Loader
---
identifier {current}
device partition=C:
path\Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
osdevicepartition=C:
systemroot \Windows
resumeobject{6abef735-3411-11de-8ea8-ac010edf8f1e}
nx OptIn
Real-mode Boot Sector
-
identifier {503bf9ab-30c8-11e1-9d62-08002700a8c7}
device partition=D:
path\ubuntu\winboot\wubildr.mbr
description Ubuntu
Don't know how to fix and the more I read the more I get confused!!!
Steve
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Repairing a dualboot Ubuntu-XP system
This is what I did from a live cd: su mount /dev/sda6 /mnt grub-install --root-directory=/mnt /dev/sda reboot then sudo update-grub replace sda6 with your partition Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diagnosing Faulty HDD
If your netbook has a CD drive try this: http://www.ultimatebootcd.com/ Can put it on a flash drive, but you will need an external CD drive or access to a laptop/desktop. Sounds to me like it is more likely to be virus related (windows opening by themselves...) Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diagnosing Faulty HDD
Also download an antivirus rescue live USB/CD e.g. http://www.avg.com/gb-en/avg-rescue-cd-download Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Top Posting
I hate bottom posting, I don't want to scan/re-read a thread I have been following over and over. I always delete the original email I reply to and quote it where ever necessary. This is particularly bad if someone replies to a digest, I just give up! Some of the guys on my local LUG are totally obsessed with bottom posting and with HTML email, life is too short. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Problem when powering off - suspend light flashing
Coming out of standby is a major issue on a lot of machines. Usually a problem with the video drivers (but not always). What video card do you have? My machine will not come out of standby 90% of the time running FGLRX radeon drivers, but does on the open source drivers, works as good as gold on the open source version. Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] uname -a for 32 bit os on 64 bit cpu
For hardware info, I use the inxi script e.g (from my debian install): $ inxi -F System:Host: n5010 Kernel: 3.0.0-1-amd64 x86_64 (64 bit) Desktop Gnome 2.30.2 Distro: Linux Mint Debian Edition Machine: Mobo: Dell model: 03C6YH version: A15 Bios: Dell version: A15 date: 07/19/2011 CPU: Dual core Intel Core i5 CPU M 430 (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) Clock Speeds: 1: 1197.00 MHz 2: 1197.00 MHz 3: 1197.00 MHz 4: 1197.00 MHz Graphics: Card: ATI Manhattan [Mobility Radeon HD 5400 Series] X.Org: 1.11.1.902 drivers: ati,radeon (unloaded: vesa,fbdev) Resolution: 1366x768@60.0hz GLX Renderer: Gallium 0.4 on AMD CEDAR GLX Version: 2.1 Mesa 7.11 Audio: Card-1: Intel 5 Series/3400 Series Chipset High Definition Audio driver: HDA Intel Sound: ALSA ver: 1.0.24 Card-2: ATI Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] driver: HDA Intel Network: Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 IF: eth1 state: down speed: 10 Mbps duplex: half mac: a4:ba:db:ba:04:f2 Card-2: Broadcom BCM4313 802.11b/g/n Wireless LAN Controller driver: wl IF: eth2 state: up mac: 70:f1:a1:55:fe:bf Drives:HDD Total Size: 500.1GB (18.8% used) 1: /dev/sda WDC_WD5000BEVT 500.1GB Partition: ID: / size: 46G used: 7.5G (18%) fs: ext4 ID: /home size: 221G used: 81G (39%) fs: ext4 ID: swap-1 size: 8.00GB used: 0.00GB (0%) fs: swap Sensors: System Temperatures: cpu: 65.5C mobo: N/A gpu: 73.5 Fan Speeds (in rpm): cpu: N/A Info: Processes: 208 Uptime: 3:41 Memory: 1973.9/3831.4MB Client: Shell inxi: 1.7.24 -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Recovery with live CD
On 19 October 2011 12:02, alan c aecl...@candt.waitrose.com wrote: On 19/10/11 09:29, ** wrote: I admit it I was stupid. I was doing an unattended upgrade of my laptop to 11.10 and then stupidly turned off the mains power. Needless to say the upgrade failed about an hour later and I can no longer boot to the hard disk. I can boot with a live cd (it happens to be Mint because it's all I have immediately available) on a USB stick and of course I am having trouble with file permissions trying to save my /home directory. Unfortunately when I try sudo nautilus however my hard disk is not even visible (and I get a permission denied message) although it is visible without the sudo but without the necessary permissions. After other comments here: does gksudo nautilus work? Also - is nautilus still used in Ubuntu 11.10? In a live session - iirc, then in a terminal, just su will raise you to superuser level I think, then , to start (nautilus) just nautilus (??) hth -- alan cocks Ubuntu user -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Before you launch nautilus, try mounting the drive first with from the command line or would Gparted do it??? Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora hash
I think they were too slow out of the blocks. A couple of days ago I offered my FB friends an invite, take up rate - zero. I think if Diaspora was used correctly, we could turn it into an ad hoc forum. Any test # post worked. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] What should be done for 12.04
I wish for the release cycle to slow down and attempt to fix all of the problems before the next release, instead of ploughing forward inexorably. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] What should be done for 12.04
Or should I have said +1 Simon ;) -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Language spell check firefox
Search synaptic for locales and remove the ones you do not need. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora* invites?
Sent. On 3 September 2011 23:41, Andres andre...@gmail.com wrote: ** After some time on google+ and even more time on facebook i have found i am more interested in diaspora* some time ago someone had gotten in: could I have an invite and/or join the ubuntu-uk node? -- Sent from my Nokia N900 Please do not send me word documents plain txt or pdf are prefered. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] New on-line storage contender 10gb free
http://minus.com/ Just a heads-up, thought you may be interested. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Problem Upgrading to 11.04 Desktop
I just accidentally clicked on the link (damned trackpad!) and it downloaded, so no problem here :) Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Google+
So have I (deluge of invites) :) On 10 July 2011 11:51, J Fernyhough j.fernyho...@gmail.com wrote: On 10 July 2011 11:32, Steve Flynn anothermindb...@gmail.com wrote: You're going to get a flood of people asking for invites now. ;) (me included! :D ) Done. Email inbound Apparently the method of starting a circle and adding people via email works when inviting doesn't. I suspect you could be correct there. I needed to add you to a circle, then view your profile, and then Send and Invite. Thank you muchly. I feel my geek needs sated. :) On 10 July 2011 11:41, Andrew Savin andrew.sa...@blueyonder.co.uk wrote: Any chance of an invite? Andrew Sending... Jonathon -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Google+
So the important question is how can we use Google+ in a constructive way to improve the Group/Our Lives/whatever. Diaspora contunues to be a bit of a damp squib :( Google+ is very underwhelming at the moment, all I have managed to do so far is spam people in my address book (only one mail, but to a lot of people!). Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] hard disk problem ?
Yes, a couple of times. Take this scenario: My sister bought me a CD (Free/Bad Co Greatest Hits), I stuck it in my laptop, ripped it and left in the drive. Boom, unusable system, log files fill up with errors from the CD drive and I have to boot from a live CD to delete them, still don't know why it happened. Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] hard disk problem ?
Windows pops up a Disk clean up box with a couple of gig to spare (IIRC). Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Help needed finding my bluetooth on my new laptop
I have an Acer laptop with bluetooth on keyboard, but no bluetooth installed. On my other laptop bluetooth only shows up in lsusb, not lspci. HTH Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Dad's Computer - for want of a better subject
The new hardware may not be compatible with XP, as long as the shop authenticated the Vista install, I wouldn't make a big issue about it. Just be prepared for lots of questions from your Dad, everything moved or was given a different name in Vista and the UAC is a royal PITA :) Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Dropbox type solutions....
What about: http://www.webupd8.org/2011/06/stable-sparkleshare-02-released-with.html Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Off topic - RAM
Will have a look, was clearing the attic yesterday and I saw some old ram, but I think they were only 256mb (2 off). Whats in it and does it have to be matched pairs? -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] unity gimp
How about a work-around, don't run Unity so don't know if possible and can't test. Can you attach a script to a button on the Unity bar? If so, install xdotool and put this script on the bar: #!/bin/bash xdotool search --class gimp windowactivate Definitely works from a terminal though and from compiz, but not from a run box (gmrun) - strange. Cheers Steve PS - Or does Unity use the gnome hotkey program??? -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] whatsapp
On 28 May 2011 19:26, Andres andre...@gmail.com wrote: Hi, Maybe not directly ubuntu related but I guess most of you use smartphones and are aware of what is plain bad.. Some friends have been giving me some buzz with http://www.whatsapp.com/seems like a mix of sms and IM. Do any of you use it? Is it worth installing? Andres. -- Sent from my Nokia N900 Please do not send me word documents plain txt or pdf are prefered. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ I use it on my iPhone, it is good, but now I have moved on to viber, which also has voice capabilities. Easier to use than Skype and free. Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] Synaptics trackpad - Need some help testing a little program wot I wrote
I have written a little program, scgui, a gui frontend to synclient (required obviously!). It is written in Pascal/Lazarus. It enables/disables Two finger scrolling (Horizontal and Vertical), Circular scrolling, Tap to Click and Touch pad on/off. The program does not read the current settings, when the button turns green on click, then the option is set to 1 (on) or Grey its off. So click to enable, then click again to disable. **WARNING** Touchpad off can be reversed in a terminal with synclient TouchpadOff=0 or by pressing enter in the gui. Let me know what you think. Link to my Dropbox inc source is around 1.6mb after strip/UPXing the executable. Steve http://dl.dropbox.com/u/1286239/scgui.tar.gz -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Samsung SCX-3205 PSC driver for 10.04
On 24 March 2011 19:23, Michael Daniels michae...@hotmail.co.uk wrote: Downloaded all Linux files from Samsung, but printer returns, internal error - please use the proper driver The driver CD is written for MS Windows, so no use. Any suggestions appreciated, other than the always online help brigade who can solve everything for a fee of £28 Thanks, Michael -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Have you seen this? http://ubuntuforums.org/showthread.php?t=341621page=50 Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Preferred online storage solution?
I run Spideroak and dropbox together they work well. I use spideroak for specific folders and dropbox for selected files and transferring to my cheapo tablet Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] ubuntu-uk Digest, Vol 69, Issue 59
On 26 January 2011 21:06, bod...@googlemail.com wrote: On the subject of crapware, my boss decided to try ubuntu on his new dell latitude laptop running win7, he installed it by himself, and came to me the next day when it was broken. Turns out dell wrote a dock-like application for win7, which they preinstalled and it cripples grub everytime it loads. Its not the dock, its the Dell Datasafe backup software and it only affects Grub2, doesn't affect earlier versions of Grub. Tell him to boot into windows, uninstall, re-install grub and it will work. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] netbook wifi traffic disconnects all
On 19 January 2011 23:31, Barry Titterton barry.titter...@mail.adsl4less.com wrote: On Tue, 2011-01-18 at 23:11 +, Bill Cumming wrote: I've a Netgear DG834gt Router with custom firmware, It does the same! With me It's a problem with the way the router handles ports, It only happens when i'm downloading many torrents, causes the routers wireless not respond. My router stands vertically with a 4inch gap all around it in a room with no central heating on (it's around 16c in the room) so don't think it's not an over heating problem. It sounds more like a problem with the drivers of the wireless, Can't remember where I read it but there's something about the number of ports the router can open and the speed the connections are recycled causes the drivers to effectively crash if it happens too quickly. As I said, it only happens with me If I'm downloading multiple torrents and they all try to open more than 256 ports each.. -- Regards Bill Cumming Twitter: @s0l_uk Skype: s0litaire eMail: b...@s0l.co.uk I have also had a problem recently with my DG834GT, which suddenly started dropping connections. I traced this to the channel that I was using. The router defaults to channel 6. I changed to channel 11 and the problem went away. I think that one of my neighbours must have bought a wireless device such as a base station telephone which was swamping the signal for channel 6. It is worth a try as it is simple to change and will not cost you a penny. Barry -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ My setup is a WRT54G2. If I try to torrent a distro, my Missus can't access the internet at all. I have always assumed Virgin where traffic shaping, basically stopping people downloading torrents (most of which are probably illegal!) and swamping the network. This also happens if I download a torrent in Windows, so it is not just a linux thing. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] MINT - was Distro hopping / Laptop running hot
On 20 January 2011 21:23, Barry Drake bdr...@crosswire.org wrote: On Thu, 2011-01-20 at 21:15 +, Craig Peden wrote: Linux Mint releases with a number are ubuntu based. i.e Mint 10 Julia. LMDE is debian. Tomorrow I'll try Mint DE and see what I think. Regards,Barry. -- Barry Drake is a member of the the Ubuntu Advertising team. http://ubuntuadverts.org/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Definitely worth a punt Barry: Pros: Rock solid - I haven't broken it, even with my normal tinkering :) Most PPAs I have tried work (except LibreOffice, but I got that working by downloading the Debs). Suspend works (mostly, but not at all on Ubuntu 10.04). Cons: Its not as up-to-date as I would like, kernel is only 2.6.32-5-amd64, but I am working on getting the Liquirix kernel installed (it installs OK but DKMS doesn't rebuild my wifi or ATI drivers). Overall lacks the user input of Ubuntu, Ubuntu has taken over the world though. I have found a script to duplicate add PPA functionality as well. Feel free to give me a shout, if I can help I will. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] buying a laptop?
On 18 January 2011 17:27, Barry Drake bdr...@crosswire.org wrote: On Tue, 2011-01-18 at 17:23 +, George Tripp wrote: It was pcspecialists themselves who alerted me that there was a problem! Just been put in touch with: https://www.linuxlaptops2go.co.uk/home LinuxLaptops2Go. See how you get on with them. Regards,Barry. -- Barry Drake is a member of the the Ubuntu Advertising team. http://ubuntuadverts.org/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Every laptop on that site says out of stock!! -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Distro hopping / Laptop running hot
I tried Arch in a virtual machine a while ago, it is a little bit daunting, I was just left with a command prompt, really cannot be bothered to build everything from the ground up, tinkering yes, building no :) Sabayon sounds interesting, may give it a whirl in a vm later in the week. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Distro hopping / Laptop running hot
Brilliant! :) -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Distro hopping / Laptop running hot
On 8 January 2011 23:56, Rob Beard r...@esdelle.co.uk wrote: On 08/01/11 21:22, Steve Fisher wrote: My laptop is running hot so I have spent the last couple of weeks distro-hopping on my new Dell Inspiron N5010 laptop to have a look at the competition: Mandriva - I am a refugee from Mandriva, looking bad over on the forums, hardly any one there! Worked well, hardware recognised (and I know what I am doing!) Fedora - didn't like it, could fry an egg on my trackpad! snip I find that my laptop occasionally runs hot, I tend to throttle it down to 1GHz but I do find that Flash (and Thunderbird) tend to hammer the CPU even when idle. Maybe that doesn't help. I also recently replaced my hard drive (I have an Aspire 2920 12 notebook) so I could get to the CPU fan when I had the bottom cover of the laptop off, I blew the fan and lots of fluff came flying out. The funny thing is it wasn't that long ago since I cleaned it before. Guess these things just attract dust and fluff. Oh and you must have a big trackpad, best I could manage is a blob of egg white on my trackpad. Rob -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Oh all right, a quail's egg maybe, even throttled back to 1.2ghz (lowest possible) it is still running at around 60 deg C! Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora
When did they start coming out? I signed up, but haven't seen anything (unless it got spam binned in error). I wouldn't mind an invite if there is one going :) Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora
Thanks Vinothan, I now have 5 invites on a first come basis, email me on xirco...@gmail.com Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora
Ronnie Sent. Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Diaspora handles
xir...@joindiaspora.com I like the way you can set up groups, very neat! Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] Is it safe to upgrade to 10.10 (ATI video drivers)?
Pretty much as per title, I use compiz so require it to work, when I upgraded last time it didn't. Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Is it safe to upgrade to 10.10 (ATI video drivers)?
Cheers for that, will give it a blast over Christmas Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] Somebody wanted a network monitor?
Have deleted to original mail but just spotted: http://www.webupd8.org/2010/12/do-you-have-limited-internet-plan-use.html Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Adeskbar
On 6 November 2010 20:18, Neil Greenwood neil.greenwood@gmail.comwrote: On 5 November 2010 18:43, Steve Fisher xirco...@gmail.com wrote: Just tried Adeskbar 0.4.2 - launch it (alt-f2) and I get a the bar and a flashing black box in the middle of the screen and lose control of the laptop and have to power down :( Launching from a terminal, I get no errors and can eventually ctrl+c out of it. Tried killing AWN Xcompmgr and running, same problem. Any ideas? Cheers Steve Any messages in the terminal when you run it? Try clicking the Run in terminal box in the Alt-F2 launch dialog. If you don't need to kill anything to run it successfully from the terminal, I doubt that's the problem. However, I've never tried it personally. Cofion/Regards, Neil. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ No errors (as mentioned) in fact no messages of any kind. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
[ubuntu-uk] Adeskbar
Just tried Adeskbar 0.4.2 - launch it (alt-f2) and I get a the bar and a flashing black box in the middle of the screen and lose control of the laptop and have to power down :( Launching from a terminal, I get no errors and can eventually ctrl+c out of it. Tried killing AWN Xcompmgr and running, same problem. Any ideas? Cheers Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Is grandr the best way to use digital projector?
On 4 November 2010 19:39, Dianne Reuby pramc...@yahoo.co.uk wrote: On Thu, 2010-11-04 at 14:19 +, pmgazz wrote: Agree, try it out half an hour before the audience arrives Good advice - I played for a bit, and got various configurations - my laptop on the overhead and overhead on my laptop, top half on the overhead and bottom half on my laptop, and (with help from a colleague) no boot at all! Luckily that soon went away. :) I may try again next Monday if I have time - but I can always take the cowards way out and run it in OO on one of our XP laptops. Am I allowed to say that on this list? ;) Dianne -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Heresy! :) -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Gnome-panel replacement
On 3 November 2010 19:40, bod...@googlemail.com wrote: Hi guys, I have several issues with my gnome-panel at the moment; things not showing up, swapping places etc. Before I bother trying to fix them, I was wondering if there is a decent replacement for it? I have used AWN in the past and like it, but I dislike the mac feel and I like how apps have panel icons . So does anyone know of any replacements that allow apps to still dock their panel icons? That's the main feature I need, anything else is a bonus Cheers Bodsda Sent from my BlackBerry® wireless device -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ I use AWN with Dockbarx and you can use AWN in panel mode: http://www.webupd8.org/2010/06/dockbarx-0391-finally-works-with-avant.html Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Is grandr the best way to use digital projector?
On 30 October 2010 22:18, Grant Sewell dcg...@thymox.co.uk wrote: On Sat, 30 Oct 2010 21:42:20 +0100 (BST) dianne reuby wrote: I've got an Open Office slide show on my laptop (running Ubuntu 10.10) and I want to use it with a digital projector. I've looked at grandr, but I can't find a lot of info - is this the best option? Or does it depend on my laptop specs and video card etc.? I could convert it to Windows format and use a windows laptop, but I'd have to remember to keep copying any updates over, and also remember which laptop I'd used! TIA Dianne Hi Dianne, It depends on what you want to achieve and on your laptop's hardware. For instance, if you have a laptop with an nVidia graphics chip, and if you're using the nVidia drivers, then I'd recommend using the nvidia-settings tool to set up your displays appropriately. You can quite easily set up a cloned-screen (both laptop display and the projector showing the same output) or a multi-screen (each attached display device having a different output on it) setup. Also, if you are considering using the files on a Windows machine, don't forget that you can quite easily install OpenOffice on the Windows machine too. Then you wouldn't have to keep changing formats. Grant. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Also you could setup a free dropbox account between the two laptops to sync the presentation. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] What accounting software to recommend
On 23 October 2010 12:15, Gordon Burgess-Parker gbpli...@gmail.com wrote: On 22/10/2010 21:42, Yorvyk wrote: because their book-keeper had developed a pathological hatred of Sage for some reason. I understand that. Sage is AWFUL! They were very happy with it and when they merged with another company they took to it as well and dropped Sage. Admittedly their accountants didn’t like it, as they believed Sage was the only thing worth using. Obviously a backhander there - most Management Accountants I knew also hated Sage -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ I am a Management Accountant, I dislike Sage with a vengeance. I prefer Opera my self, but I am an xBase programmer :) Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Find a Router's IP address
On 19 October 2010 18:18, Hakan Koseoglu ha...@koseoglu.org wrote: On 19/10/10 16:54, Cornelius Mostert wrote: The scenario is as follow: 1. You have permission to work as Admin on a Lan 2. You do NOT have any documentation from the previous Admin 3. You find a router / WiFi Router that is in use and therefore you can NOT reset it 4. This router is a home / consumer router like Netgear, Linksys, etc. So not an enterprise router 5. You need to brows to the routers config web page to make some changes (you assume the default admin and password for the router) BUT you do NOT know the IP address 6. You know the router is NOT a DHCP server Now the question is HOW do you find the IP address of the router ??? If it is the router providing the access outside, netstat -nr will show you the route, hence the IP address of the router. If you know which servers/clients are using it as a gateway, run those commands from there. But what then, what will knowing the IP address provide to you, I'm not sure. If the previous admin has walked away with all of the information, I'd treat that router as compromised and take it off the net ASAP and replace it with a known configuration - damn the users, just let them know about the outage. Nmap will attempt to show you any IP addresses on the network with a reasonable distinction of if the device is Netgear, Cisco etc. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ +1 for netstat -nr. Also look for a factory reset button on the router, but make sure you know the settings first! Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] Strange connection problem to Router
On a bus on my phone. Check the contents of a file I think it is: /var/lib/NetworkManager/NetworkManager.state Should have 3 or 4 lines ending in the word true. If not edit, change and reboot. Usual cause of this is a failed suspend. Will confirm file name when I get home Sent from my iPhone On 18 Oct 2010, at 16:00, John Stevenson j...@jr0cket.com wrote: On 18 October 2010 15:25, Gordon Burgess-Parker gbpli...@gmail.com wrote: I have a netgear wireless router which at the moment I am not able to use for wireless so I’m using a patch cable to the ethernet port. My Windows 7 laptop just err connects to the router and I can plug in and unplug at will, BUT, when I plug the cable into my Netbook running 10.04 it fails to connect! It shows the wired connection, but comes up with the “Wired Network disconnected” message. I’ve disabled wireless, but it won’t connect at all! Anyone know why? (I always though that with wired connections you just “plug it in”) Hello Gordon, Yes, you should just be able to plug the wire in and it just works. The network manager panel icon now is animated when it is trying to get connected using an automatically assigned network address (DHCP). The panel icon now uses the same animation for wired and wireless. It sound like it is failing to get a network address from your router. Here are some things you could try: 1) Check your router can give out more IP addresses using the web based interface on your router - I guess you will have to go into Windows for - your DHCP range of addresses should be big enough for all your computers and Internet enabled devices. 2) Check network manager for your wired setup - right click on the network incon in the panel and select Edit configurations - check the wired tab has an entry and edit that entry to ensure it is configured to use DHCP. 3) If you know your network settings, use the network manager to create a new wired entry and set up a manual network. If you are unsure of how to use network manager, have a look at page 41 onward of the ubuntu-manual http://ubuntu-manual.org/ for a very nice guide to the network manager. Hope this helps. -- John Stevenson Lean Agile Consultant / Coach jr0cket.com | leanagilemachine.com -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
On 16 October 2010 10:01, Jacob Mansfield cyberja...@gmail.com wrote: I am attempting to make the desktop background in gnome change automatically to a random image from a set folder. I know the command I need is gconftool-2 --type=string -s /desktop/gnome/background/picture_filename /full/path/to/image/file I have worked this into a basic shell script: time=$1 # time to wait between changing the background in secs while [ : ] do for filepath in `cat list` # list is a list of all files in the backgrounds directory and is the only other non-image file in the folder do echo $filepath # for debug gconftool-2 --type=string -s /desktop/gnome/background/picture_filename “$filepath” sleep $time done done however allthough this sets the value (I can see it in the xml configuration file with emacs) the background simply goes to the set colour not the image. is there another value I need to get the background as an image? or is there something wrong with my script? all help appreciated. Jacob Mansfield Programmer -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/ Jacob Have a look at: http://www.itlure.com/2009/11/create-your-own-gnome-background.html Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
Thinking out of the box, why not write a script to generate the xml file? I will have a go, but have to nip out for a couple of hours. Steve -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
God, this was hard work! But I think it runs, needs testing and all the
paths are hardcoded and need changing.
So I am assembling a directory of jpegs and will report back, but going out
(again) for a while.
#!/bin/bash
rm background-1.xml
echo background background-1.xml
echo starttime background-1.xml
echo year2009/year background-1.xml
echo month08/month background-1.xml
echo day04/day background-1.xml
echo hour00/hour background-1.xml
echo minute00/minute background-1.xml
echo second00/second background-1.xml
echo /starttime background-1.xml
echo !-- This animation will start at midnight. -- background-1.xml
#counter variable
x=1
for file in *
do
#echo $x
if [ $x -eq 1 ]
then
FE='to/usr/share/backgrounds/cosmos/'
FE=${FE}$file
FE=${FE}/to
fi
if [ $x -gt 1 ]
then
FT='to/usr/share/backgrounds/cosmos/'
FT=${FT}$file
FT=${FT}/to
echo $FT background-1.xml
fi
echo static background-1.xml
echo duration1795.0/duration background-1.xml
FS= file/usr/share/backgrounds/cosmos/
FS=${FS}$file
FS=${FS}/file
FR= from/usr/share/backgrounds/cosmos/
FR=${FR}$file
FR=${FR}/from
FT= to/usr/share/backgrounds/cosmos/
FT=${FT}$file
FT=${FT}/to
echo $FS background-1.xml
echo static background-1.xml
echo duration5.0/duration background-1.xml
echo $FR background-1.xml
echo /transition background-1.xml
#ls $file # Lists all files in $PWD (current directory).
x=$(( $x + 1 ))
#echo $x
done
echo $FE background-1.xml
echo /transition background-1.xml
echo /background background-1.xml
exit 0
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
OK script finished tested and working:
#!/bin/bash
rm background-2.xml
echo background background-2.xml
echo starttime background-2.xml
echo year2009/year background-2.xml
echo month08/month background-2.xml
echo day04/day background-2.xml
echo hour00/hour background-2.xml
echo minute00/minute background-2.xml
echo second00/second background-2.xml
echo /starttime background-2.xml
echo !-- This animation will start at midnight. -- background-2.xml
#counter variable
x=1
for file in *.jpg
do
if [ $x -eq 1 ]
then
FE='to/usr/share/backgrounds/testdir/'
FE=${FE}$file
FE=${FE}/to
fi
if [ $x -gt 1 ]
then
FT='to/usr/share/backgrounds/testdir/'
FT=${FT}$file
FT=${FT}/to
echo $FT background-2.xml
echo /transition background-2.xml
fi
echo static background-2.xml
echo duration1795.0/duration background-2.xml
FS= file/usr/share/backgrounds/testdir/
FS=${FS}$file
FS=${FS}/file
FR= from/usr/share/backgrounds/testdir/
FR=${FR}$file
FR=${FR}/from
FT= to/usr/share/backgrounds/testdir/
FT=${FT}$file
FT=${FT}/to
echo $FS background-2.xml
echo /static background-2.xml
echo transition background-2.xml
echo duration5.0/duration background-2.xml
echo $FR background-2.xml
#ls $file # Lists all files in $PWD (current directory).
x=$(( $x + 1 ))
#echo $x
done
echo $FE background-2.xml
echo /transition background-2.xml
echo /background background-2.xml
exit 0
Change /usr/share/backgrounds/testdir/ to match your directory with search
replace.
Will tart it up with zenity later.
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
Instructions: 1. Dump a load of jpegs in a directory, I used /usr/backgrounds/testdir 2. Copy the script into the same directory and make it executable. Edit and change path and name of output xml to suite. 3. Open terminal change directory and run script 4. Drag and drop output xml to background section of appearance. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] gnome desktop background changer
Ha Ha Ha http://darkrule.freewebhostx.com/hello/xmlmaker.php http://darkrule.freewebhostx.com/hello/xmlmaker.phpIf only I had read further down the link I originally gave you. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
