Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Debian User (http://www.linux-archive.org/debian-user/)
-   -   power interruption -> renamed USB disk (http://www.linux-archive.org/debian-user/498435-power-interruption-renamed-usb-disk.html)

Ross Boylan 03-07-2011 08:08 PM

power interruption -> renamed USB disk
 
I have a SATA disk in an external USB docking station. The computer it
is attached to is on UPS, but the external disk has only surge
protection.

When the power goes out for a moment, the disk, which was /dev/sdc,
seems to come back as /dev/sdd. The disk has a partition that is part
of an LVM volume group, and the file system on the disk is inaccessible.

I've had to restart the system to get the disk back.

Is there a better way (aside from getting the disk on UPS)?

Debian Lenny (mostly), 2.6.26-2-686 stock Debian kernel on Pentium 4
chip w/hyperthreading. The disk uses the GPT partition format.

Most recent incident:
<log>
#power fails
Mar 7 11:21:18 corn kernel: [182529.931888] ethfast: Link is Down
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3: USB disconnect, address 4
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.1: USB disconnect, address 7
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.2: USB disconnect, address 8
Mar 7 11:21:18 corn kernel: [182530.140155] usblp0: removed
Mar 7 11:21:18 corn kernel: [182530.375701] usb 5-4: USB disconnect, address 5
#power resumes
Mar 7 11:21:21 corn kernel: [182533.121591] usb 5-3: new high speed USB device using ehci_hcd and address 9
Mar 7 11:21:21 corn kernel: [182533.179788] hub 5-0:1.0: unable to enumerate USB device on port 3
Mar 7 11:21:30 corn kernel: [182542.755370] __ratelimit: 4 messages suppressed
Mar 7 11:21:30 corn kernel: [182542.755379] Buffer I/O error on device dm-15, logical block 8210
Mar 7 11:21:30 corn kernel: [182542.755384] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.755480] ReiserFS: dm-15: warning: journal-837: IO error during journal replay
Mar 7 11:21:30 corn kernel: [182542.755480] REISERFS: abort (device dm-15): Write error while updating journal header in flush_journal_list
Mar 7 11:21:30 corn kernel: [182542.755480] REISERFS: Aborting journal for filesystem on dm-15
Mar 7 11:21:30 corn kernel: [182542.755480] Buffer I/O error on device dm-15, logical block 418
Mar 7 11:21:30 corn kernel: [182542.755480] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 419
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 420
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 421
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 422
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 423
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 424
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 425
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.761971] Buffer I/O error on device dm-15, logical block 426
Mar 7 11:21:30 corn kernel: [182542.761971] lost page write due to I/O error on dm-15
Mar 7 11:21:30 corn kernel: [182542.762384] ReiserFS: dm-15: warning: clm-6006: writing inode 2353029 on readonly FS
Mar 7 11:21:30 corn kernel: [182543.243725] usb 5-3: new high speed USB device using ehci_hcd and address 10
Mar 7 11:21:30 corn kernel: [182543.392646] usb 5-3: configuration #1 chosen from 1 choice
Mar 7 11:21:30 corn kernel: [182543.394112] hub 5-3:1.0: USB hub found
Mar 7 11:21:30 corn kernel: [182543.395207] hub 5-3:1.0: 4 ports detected
Mar 7 11:21:30 corn kernel: [182543.501289] usb 5-3: New USB device found, idVendor=1a40, idProduct=0101
Mar 7 11:21:30 corn kernel: [182543.501298] usb 5-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Mar 7 11:21:30 corn kernel: [182543.501303] usb 5-3: Product: USB 2.0 Hub [MTT]
Mar 7 11:21:31 corn kernel: [182543.752650] usb 5-4: new high speed USB device using ehci_hcd and address 11
Mar 7 11:21:31 corn kernel: [182543.828137] ethfast: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Mar 7 11:21:31 corn kernel: [182543.828137] ethfast: 10/100 speed: disabling TSO
Mar 7 11:21:31 corn kernel: [182543.895490] usb 5-4: configuration #1 chosen from 1 choice
Mar 7 11:21:31 corn kernel: [182543.899493] usb 5-4: New USB device found, idVendor=04b8, idProduct=011e
Mar 7 11:21:31 corn kernel: [182543.899493] usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 7 11:21:31 corn kernel: [182543.899493] usb 5-4: Product: EPSON Scanner
Mar 7 11:21:31 corn kernel: [182543.899493] usb 5-4: Manufacturer: EPSON
Mar 7 11:21:33 corn kernel: [182546.073233] usb 5-3.2: new high speed USB device using ehci_hcd and address 12
Mar 7 11:21:33 corn kernel: [182546.172447] usb 5-3.2: configuration #1 chosen from 1 choice
Mar 7 11:21:33 corn kernel: [182546.172447] usblp0: USB Bidirectional printer dev 12 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0022
Mar 7 11:21:33 corn kernel: [182546.173904] usb 5-3.2: New USB device found, idVendor=04f9, idProduct=0022
Mar 7 11:21:33 corn kernel: [182546.173904] usb 5-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 7 11:21:33 corn kernel: [182546.173904] usb 5-3.2: Product: HL-5150D
Mar 7 11:21:33 corn kernel: [182546.173904] usb 5-3.2: Manufacturer: Brother
Mar 7 11:21:33 corn kernel: [182546.173904] usb 5-3.2: SerialNumber: K4J587961
Mar 7 11:21:45 corn kernel: [182558.721983] usb 5-3.1: new high speed USB device using ehci_hcd and address 13
Mar 7 11:21:45 corn kernel: [182558.831699] usb 5-3.1: configuration #1 chosen from 1 choice
Mar 7 11:21:45 corn kernel: [182558.840748] scsi3 : SCSI emulation for USB Mass Storage devices
Mar 7 11:21:45 corn kernel: [182558.841637] usb-storage: device found at 13
Mar 7 11:21:45 corn kernel: [182558.841637] usb-storage: waiting for device to settle before scanning
Mar 7 11:21:45 corn kernel: [182558.843187] usb 5-3.1: New USB device found, idVendor=05e3, idProduct=0718
Mar 7 11:21:45 corn kernel: [182558.843187] usb 5-3.1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
Mar 7 11:21:45 corn kernel: [182558.843187] usb 5-3.1: Product: USB Storage
Mar 7 11:21:45 corn kernel: [182558.843187] usb 5-3.1: SerialNumber: 000000000033
Mar 7 11:21:50 corn kernel: [182564.109577] usb-storage: device scan complete
Mar 7 11:21:50 corn kernel: [182564.120422] scsi 3:0:0:0: Direct-Access WDC WD20 EARS-00MVWB0 0009 PQ: 0 ANSI: 0
Mar 7 11:21:50 corn kernel: [182564.120864] sd 3:0:0:0: [sdd] 3907029164 512-byte hardware sectors (2000399 MB)
Mar 7 11:21:50 corn kernel: [182564.121231] sd 3:0:0:0: [sdd] Write Protect is off
Mar 7 11:21:50 corn kernel: [182564.121238] sd 3:0:0:0: [sdd] Mode Sense: 03 00 00 00
Mar 7 11:21:50 corn kernel: [182564.121244] sd 3:0:0:0: [sdd] Assuming drive cache: write through
Mar 7 11:21:50 corn kernel: [182564.122131] sd 3:0:0:0: [sdd] 3907029164 512-byte hardware sectors (2000399 MB)
Mar 7 11:21:50 corn kernel: [182564.123130] sd 3:0:0:0: [sdd] Write Protect is off
Mar 7 11:21:50 corn kernel: [182564.123137] sd 3:0:0:0: [sdd] Mode Sense: 03 00 00 00
Mar 7 11:21:50 corn kernel: [182564.123141] sd 3:0:0:0: [sdd] Assuming drive cache: write through
Mar 7 11:21:50 corn kernel: [182564.123147] sdd: sdd1 sdd2
Mar 7 11:21:50 corn kernel: [182564.181578] sd 3:0:0:0: [sdd] Attached SCSI disk
Mar 7 11:21:59 corn kernel: [182573.966058] ethfast: Link is Down
Mar 7 11:22:01 corn kernel: [182576.033698] ethfast: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Mar 7 11:22:01 corn kernel: [182576.033698] ethfast: 10/100 speed: disabling TSO
Mar 7 11:38:38 corn kernel: [183622.652570] ReiserFS: dm-15: warning: zam-7001: io error in reiserfs_find_entry
Mar 7 11:43:31 corn kernel: [183936.863472] fuse exit
Mar 7 11:43:33 corn kernel: [183938.589854] nfsd: last server has exited
Mar 7 11:43:33 corn kernel: [183938.614722] nfsd: unexporting all filesystems
</log>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1299532139.11656.23.camel@corn.betterworld.us">htt p://lists.debian.org/1299532139.11656.23.camel@corn.betterworld.us

Ron Johnson 03-07-2011 11:02 PM

power interruption -> renamed USB disk
 
On 03/07/2011 03:08 PM, Ross Boylan wrote:

I have a SATA disk in an external USB docking station. The computer it
is attached to is on UPS, but the external disk has only surge
protection.

When the power goes out for a moment, the disk, which was /dev/sdc,
seems to come back as /dev/sdd. The disk has a partition that is part
of an LVM volume group, and the file system on the disk is inaccessible.

I've had to restart the system to get the disk back.

Is there a better way (aside from getting the disk on UPS)?

Debian Lenny (mostly), 2.6.26-2-686 stock Debian kernel on Pentium 4
chip w/hyperthreading. The disk uses the GPT partition format.

Most recent incident:
<log>
#power fails
Mar 7 11:21:18 corn kernel: [182529.931888] ethfast: Link is Down
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3: USB disconnect, address 4
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.1: USB disconnect, address 7
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.2: USB disconnect, address 8
Mar 7 11:21:18 corn kernel: [182530.140155] usblp0: removed
Mar 7 11:21:18 corn kernel: [182530.375701] usb 5-4: USB disconnect, address 5
#power resumes
Mar 7 11:21:21 corn kernel: [182533.121591] usb 5-3: new high speed USB device using ehci_hcd and address 9
Mar 7 11:21:21 corn kernel: [182533.179788] hub 5-0:1.0: unable to enumerate USB device on port 3
Mar 7 11:21:30 corn kernel: [182542.755370] __ratelimit: 4 messages suppressed
Mar 7 11:21:30 corn kernel: [182542.755379] Buffer I/O error on device dm-15, logical block 8210
Mar 7 11:21:30 corn kernel: [182542.755384] lost page write due to I/O error on dm-15

[snip]

Mar 7 11:43:33 corn kernel: [183938.589854] nfsd: last server has exited
Mar 7 11:43:33 corn kernel: [183938.614722] nfsd: unexporting all filesystems
</log>



Why are you using device names instead of labels or UUIDs?

--
I prefer banana-flavored energy bars made from tofu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4D75722C.8080200@cox.net">http://lists.debian.org/4D75722C.8080200@cox.net

Ross Boylan 03-08-2011 04:25 AM

power interruption -> renamed USB disk
 
On Mon, 2011-03-07 at 18:02 -0600, Ron Johnson wrote:
> On 03/07/2011 03:08 PM, Ross Boylan wrote:
> > I have a SATA disk in an external USB docking station. The computer it
> > is attached to is on UPS, but the external disk has only surge
> > protection.
> >
> > When the power goes out for a moment, the disk, which was /dev/sdc,
> > seems to come back as /dev/sdd. The disk has a partition that is part
> > of an LVM volume group, and the file system on the disk is inaccessible.
> >
> > I've had to restart the system to get the disk back.
> >
> > Is there a better way (aside from getting the disk on UPS)?
> >
> > Debian Lenny (mostly), 2.6.26-2-686 stock Debian kernel on Pentium 4
> > chip w/hyperthreading. The disk uses the GPT partition format.
> >
> > Most recent incident:
> > <log>
> > #power fails
> > Mar 7 11:21:18 corn kernel: [182529.931888] ethfast: Link is Down
> > Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3: USB disconnect, address 4
> > Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.1: USB disconnect, address 7
> > Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.2: USB disconnect, address 8
> > Mar 7 11:21:18 corn kernel: [182530.140155] usblp0: removed
> > Mar 7 11:21:18 corn kernel: [182530.375701] usb 5-4: USB disconnect, address 5
> > #power resumes
> > Mar 7 11:21:21 corn kernel: [182533.121591] usb 5-3: new high speed USB device using ehci_hcd and address 9
> > Mar 7 11:21:21 corn kernel: [182533.179788] hub 5-0:1.0: unable to enumerate USB device on port 3
> > Mar 7 11:21:30 corn kernel: [182542.755370] __ratelimit: 4 messages suppressed
> > Mar 7 11:21:30 corn kernel: [182542.755379] Buffer I/O error on device dm-15, logical block 8210
> > Mar 7 11:21:30 corn kernel: [182542.755384] lost page write due to I/O error on dm-15
> [snip]
> > Mar 7 11:43:33 corn kernel: [183938.589854] nfsd: last server has exited
> > Mar 7 11:43:33 corn kernel: [183938.614722] nfsd: unexporting all filesystems
> > </log>
> >
>
> Why are you using device names instead of labels or UUIDs?
/dev/sdc (or sdd on power resume) is what the kernel is handing me; is
there a way to change that?

My understanding is that LVM uses UUID's, which makes its failure to
recover a bit more puzzling to me.

I suspect I'm not fully understanding the question.
Ross


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1299561953.11656.48.camel@corn.betterworld.us">htt p://lists.debian.org/1299561953.11656.48.camel@corn.betterworld.us

Ron Johnson 03-08-2011 04:47 AM

power interruption -> renamed USB disk
 
On 03/07/2011 11:25 PM, Ross Boylan wrote:

On Mon, 2011-03-07 at 18:02 -0600, Ron Johnson wrote:

On 03/07/2011 03:08 PM, Ross Boylan wrote:

I have a SATA disk in an external USB docking station. The computer it
is attached to is on UPS, but the external disk has only surge
protection.

When the power goes out for a moment, the disk, which was /dev/sdc,
seems to come back as /dev/sdd. The disk has a partition that is part
of an LVM volume group, and the file system on the disk is inaccessible.

I've had to restart the system to get the disk back.

Is there a better way (aside from getting the disk on UPS)?

Debian Lenny (mostly), 2.6.26-2-686 stock Debian kernel on Pentium 4
chip w/hyperthreading. The disk uses the GPT partition format.

Most recent incident:
<log>
#power fails
Mar 7 11:21:18 corn kernel: [182529.931888] ethfast: Link is Down
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3: USB disconnect, address 4
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.1: USB disconnect, address 7
Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.2: USB disconnect, address 8
Mar 7 11:21:18 corn kernel: [182530.140155] usblp0: removed
Mar 7 11:21:18 corn kernel: [182530.375701] usb 5-4: USB disconnect, address 5
#power resumes
Mar 7 11:21:21 corn kernel: [182533.121591] usb 5-3: new high speed USB device using ehci_hcd and address 9
Mar 7 11:21:21 corn kernel: [182533.179788] hub 5-0:1.0: unable to enumerate USB device on port 3
Mar 7 11:21:30 corn kernel: [182542.755370] __ratelimit: 4 messages suppressed
Mar 7 11:21:30 corn kernel: [182542.755379] Buffer I/O error on device dm-15, logical block 8210
Mar 7 11:21:30 corn kernel: [182542.755384] lost page write due to I/O error on dm-15

[snip]

Mar 7 11:43:33 corn kernel: [183938.589854] nfsd: last server has exited
Mar 7 11:43:33 corn kernel: [183938.614722] nfsd: unexporting all filesystems
</log>



Why are you using device names instead of labels or UUIDs?

/dev/sdc (or sdd on power resume) is what the kernel is handing me; is
there a way to change that?

My understanding is that LVM uses UUID's, which makes its failure to
recover a bit more puzzling to me.

I suspect I'm not fully understanding the question.


You appear to understand the question... :)

Re-reading your post, I see, "for a moment". How much of a moment?
IOW, does the machine go down, or just the external enclosure? If
just the enclosure, then the kernel probably thinks that the
external drives are still there.


That leads to these questions:

1. Is the LV made up of both external *and* internal drives,
or just external?

2. When the power flickers, do you do this:
# lvchange -an ${VG}/${LV}
# vgchange -an ${VG}
[unplug/wait/replug the enclosure]
# vgchange -ay ${VG}
# lvchange -ay ${VG}/${LV}

--
I prefer banana-flavored energy bars made from tofu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4D75C2E4.2030707@cox.net">http://lists.debian.org/4D75C2E4.2030707@cox.net

Ross Boylan 03-08-2011 06:20 AM

power interruption -> renamed USB disk
 
On Mon, 2011-03-07 at 23:47 -0600, Ron Johnson wrote:
> On 03/07/2011 11:25 PM, Ross Boylan wrote:
> > On Mon, 2011-03-07 at 18:02 -0600, Ron Johnson wrote:
> >> On 03/07/2011 03:08 PM, Ross Boylan wrote:
> >>> I have a SATA disk in an external USB docking station. The computer it
> >>> is attached to is on UPS, but the external disk has only surge
> >>> protection.
> >>>
> >>> When the power goes out for a moment, the disk, which was /dev/sdc,
> >>> seems to come back as /dev/sdd. The disk has a partition that is part
> >>> of an LVM volume group, and the file system on the disk is inaccessible.
> >>>
> >>> I've had to restart the system to get the disk back.
> >>>
> >>> Is there a better way (aside from getting the disk on UPS)?
> >>>
> >>> Debian Lenny (mostly), 2.6.26-2-686 stock Debian kernel on Pentium 4
> >>> chip w/hyperthreading. The disk uses the GPT partition format.
> >>>
> >>> Most recent incident:
> >>> <log>
> >>> #power fails
> >>> Mar 7 11:21:18 corn kernel: [182529.931888] ethfast: Link is Down
> >>> Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3: USB disconnect, address 4
> >>> Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.1: USB disconnect, address 7
> >>> Mar 7 11:21:18 corn kernel: [182530.140155] usb 5-3.2: USB disconnect, address 8
> >>> Mar 7 11:21:18 corn kernel: [182530.140155] usblp0: removed
> >>> Mar 7 11:21:18 corn kernel: [182530.375701] usb 5-4: USB disconnect, address 5
> >>> #power resumes
> >>> Mar 7 11:21:21 corn kernel: [182533.121591] usb 5-3: new high speed USB device using ehci_hcd and address 9
> >>> Mar 7 11:21:21 corn kernel: [182533.179788] hub 5-0:1.0: unable to enumerate USB device on port 3
> >>> Mar 7 11:21:30 corn kernel: [182542.755370] __ratelimit: 4 messages suppressed
> >>> Mar 7 11:21:30 corn kernel: [182542.755379] Buffer I/O error on device dm-15, logical block 8210
> >>> Mar 7 11:21:30 corn kernel: [182542.755384] lost page write due to I/O error on dm-15
> >> [snip]
> >>> Mar 7 11:43:33 corn kernel: [183938.589854] nfsd: last server has exited
> >>> Mar 7 11:43:33 corn kernel: [183938.614722] nfsd: unexporting all filesystems
> >>> </log>
> >>>
> >>
> >> Why are you using device names instead of labels or UUIDs?
> > /dev/sdc (or sdd on power resume) is what the kernel is handing me; is
> > there a way to change that?
> >
> > My understanding is that LVM uses UUID's, which makes its failure to
> > recover a bit more puzzling to me.
> >
> > I suspect I'm not fully understanding the question.
>
> You appear to understand the question... :)
>
> Re-reading your post, I see, "for a moment". How much of a moment?
>From a fraction of a second to a minute. Usually a fraction of a
second, though in the log above, about 3 seconds.
> IOW, does the machine go down,
IOW=?
The machine is on UPS and stays up.
> or just the external enclosure?
The external drive bay is plugged into a surge protector; it loses
power.

I suppose one complication is that the docking base may draw some power
from the USB cable when the external power fails.

> If
> just the enclosure, then the kernel probably thinks that the
> external drives are still there.
I think that would be OK (except for some lost disk activity) if the
kernel didn't think the external disk had moved to a new location
(i.e., /dev/sdd).

I speculate that hotplug hasn't quite gotten (or never gets) the news
the sdc has disappeared, and when it detects a "new" drive it assigns it
the next available location, sdd. But I'm not even sure what the
division of responsibility is between the kernel proper and the hotplug
system. I thought hotplug was supposed to ensure that the same physical
device would end up with the same name every time.
>
> That leads to these questions:
>
> 1. Is the LV made up of both external *and* internal drives,
> or just external?
The LV is in a VG that includes external and internal drives. The
particular LVs that have trouble are entirely on the external drive.
>
> 2. When the power flickers, do you do this:
> # lvchange -an ${VG}/${LV}
> # vgchange -an ${VG}
> [unplug/wait/replug the enclosure]
> # vgchange -ay ${VG}
> # lvchange -ay ${VG}/${LV}
>
No. The vgchange -an seems problematic since essentially my entire
system is on the VG. I think that means lvm would not let me deactivate
it; certainly if I succeeded I would be unable to do much of anything.
The VG is lvm2 format.

Ross



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1299568801.11656.67.camel@corn.betterworld.us">htt p://lists.debian.org/1299568801.11656.67.camel@corn.betterworld.us

Ron Johnson 03-08-2011 09:38 AM

power interruption -> renamed USB disk
 
On 03/08/2011 01:20 AM, Ross Boylan wrote:

On Mon, 2011-03-07 at 23:47 -0600, Ron Johnson wrote:

[snip]

IOW=?


In Other Words.

[snip]


I speculate that hotplug hasn't quite gotten (or never gets) the news
the sdc has disappeared, and when it detects a "new" drive it assigns it
the next available location, sdd. But I'm not even sure what the
division of responsibility is between the kernel proper and the hotplug
system. I thought hotplug was supposed to ensure that the same physical
device would end up with the same name every time.


You'd think; the power failure probably exposes an edge case.



That leads to these questions:

1. Is the LV made up of both external *and* internal drives,
or just external?

The LV is in a VG that includes external and internal drives. The
particular LVs that have trouble are entirely on the external drive.


2. When the power flickers, do you do this:
# lvchange -an ${VG}/${LV}
# vgchange -an ${VG}
[unplug/wait/replug the enclosure]
# vgchange -ay ${VG}
# lvchange -ay ${VG}/${LV}


No. The vgchange -an seems problematic since essentially my entire
system is on the VG.


Maybe just "bounce" the LV?


I think that means lvm would not let me deactivate
it; certainly if I succeeded I would be unable to do much of anything.
The VG is lvm2 format.



Hmmm. I think I'd not have designed things that way. Anyhoo,
what's there is there...


--
I prefer banana-flavored energy bars made from tofu.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4D760732.6010305@cox.net">http://lists.debian.org/4D760732.6010305@cox.net


All times are GMT. The time now is 05:21 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.