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

Re: [dm-devel] Stopped disk causes LVM to go crazy



hi. Thanks for your reply. Well, I had tried that before, but no luck. I tried it again, and still no luck:
> vgchange -an disk2
  0 logical volume(s) in volume group "disk2" now active
> sdparm -C stop /dev/sdb
> lvscan
end_request: I/O error, dev sdb, sector 0
printk: 72 messages suppressed.
Buffer I/O error on device sdb, logical block 0
Buffer I/O error on device sdb, logical block 1
Buffer I/O error on device sdb, logical block 2
Buffer I/O error on device sdb, logical block 3
end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
  end_request: I/O error, dev sdb, sector 287277824
/dev/sdb: read failed after 0 of 4096 at 0: Input/output error
end_request: I/O error, dev sdb, sector 0
  /dev/sdb: read failed after 0 of 4096 at 147086245888: Input/oend_request: I/O error, dev sdb, sector 287274137
utput error
  /dev/sdb: read failed after 0 of 4096 at 0: Inputend_request: I/O error, dev sdb, sector 287258265
/output error
  /dev/sdb1: read failed after 0 of 512 at 812646end_request: I/O error, dev sdb, sector 287258029
4: Input/output error
  /dev/sdb1: read failed after 0 of 2048 end_request: I/O error, dev sdb, sector 281410605
at 0: Input/output error
  /dev/sdb2: read failed after 0 of 20end_request: I/O error, dev sdb, sector 281410367
48 at 2993881088: Input/output error
  /dev/sdb2: read failed aend_request: I/O error, dev sdb, sector 63
fter 0 of 2048 at 0: Input/output error
  /dev/sdb4: read failed after 0 of 1024 at 144082075648: Input/output error
  /dev/sdb4: read failed after 0 of 2048 at 0: Input/output error
  ACTIVE            '/dev/disk1/blah' [10.00 GB] inherit
  ACTIVE            '/dev/disk1/blah' [100.00 MB] inherit
  ACTIVE            '/dev/disk1/blah' [10.00 GB] inherit
  ACTIVE            '/dev/disk1/blah' [100.00 MB] inherit
  ACTIVE            '/dev/disk1/blah' [10.00 GB] inherit
  ACTIVE            '/dev/disk1/blah' [100.00 MB] inherit

I'm using older LVM version:
> lvscan --version
  LVM version:     2.02.25 (2007-04 27)
  Library version: 1.02.19 (2007-04-27)
  Driver version:  4.11.0

Any ideas?

Thanks

----- Original Message -----
From: "Bryn M. Reeves" <bmr redhat com>
To: "device-mapper development" <dm-devel redhat com>
Sent: Wednesday, February 11, 2009 2:39:20 AM GMT -08:00 US/Canada Pacific
Subject: Re: [dm-devel] Stopped disk causes LVM to go crazy

Alireza Nematollahi wrote:
> hi guys,
>
> I have a system with two SATA disks and I have LVM on the disks. I
> use sdparm (sdparm -C stop /dev/sdb) to spin-down one of them. It
> works fine and I can hear the disk spinning down and all...But when
> I run any LVM command, say lvscan or whatever, I get lots of error
> messages:

What did you expect? :)

If the volume group is active when you remove/spin down the disks LVM
has no way of knowing that you wanted to do that. To the software, it
just looks like a drive has failed or gone away while it was in use.

<snip>

> /dev/sdb2: read failed after 0 of 4096 at 2993881088: Input/output
> error /dev/sdb2: read failed after 0 of 4096 at 0: Input/output
> error /dev/sdb4: read failed after 0 of 1024 at 144082075648:
> Input/output error /dev/sdb4: read failed after 0 of 2048 at 0:

> Input/output error Even when I physically remove the disk it still
> happens. Is there any way I can stop LVM from querying both disks
> or at least to stop displaying the error messages?

Tell LVM to stop using the disk first. See the man page for vgchange
for full details but you want to run:

vgchange -an <volume group>

To deactivate the volume group *before* you start removing devices
that it is using.

Regards,
Bryn.

--
dm-devel mailing list
dm-devel redhat com
https://www.redhat.com/mailman/listinfo/dm-devel

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