Dr. Martin Mundschenk
2009-Dec-12 14:48 UTC
[zfs-discuss] Messed up zpool (double device label)
Hi!
I tried to add an other FiweFire Drive to my existing four devices but it turned
out, that the OpenSolaris IEEE1394 support doen''t seem to be
well-engineered.
After not recognizing the new device and exporting and importing the existing
zpool, I get this zpool status:
pool: tank
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using ''zpool replace''.
see: http://www.sun.com/msg/ZFS-8000-4J
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
tank DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
c12t0d0 ONLINE 0 0 0
c12t0d0 FAULTED 0 0 0 corrupted data
c14t0d0 ONLINE 0 0 0
c15t0d0 ONLINE 0 0 0
The device c12t0d0 appears two times!?
''format'' returns these devices:
AVAILABLE DISK SELECTIONS:
0. c7d0 <DEFAULT cyl 19454 alt 2 hd 255 sec 63>
/pci at 0,0/pci-ide at b/ide at 0/cmdk at 0,0
1. c12t0d0 <Ext Hard- Disk--931.51GB>
/pci at 0,0/pci10de,ac7 at 16/pci11c1,5900 at 0/unit at
00303c02e014fc66/disk at 0,0
2. c13t0d0 <Ext Hard- Disk--931.51GB>
/pci at 0,0/pci10de,ac7 at 16/pci11c1,5900 at 0/unit at
00303c02e014fc32/disk at 0,0
3. c14t0d0 <Ext Hard- Disk--931.51GB>
/pci at 0,0/pci10de,ac7 at 16/pci11c1,5900 at 0/unit at
00303c02e014fc61/disk at 0,0
4. c15t0d0 <Ext Hard- Disk--931.51GB>
/pci at 0,0/pci10de,ac7 at 16/pci11c1,5900 at 0/unit at
00303c02e014fc9d/disk at 0,0
When I scrub data, the devices c12t0d0, c13t0d0 and c14t0d0 re accessed and
c15t0d0 sleeps. I don''t get it! How can such a mess happen and how do I
get it back straight?
Regards,
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091212/4b1a3cb8/attachment.html>
Maybe Matching Threads
- Extremely slow raidz resilvering
- lilo causes a "Unexpected dirty buffer encountered at do_get_write_access:597 (03:02 blocknr 0)"
- [BUG] linux-2.4.7-ac7 Assertion failure in journal_revoke() at revoke.c:307
- Checksum errors on and after resilver
- Changing root journal data mode
