Interesting, this time it worked! Does specifying the device to clear
cause the command to behave differently? I had assumed w/out the device
specification, the clear would just apply to all devices in the pool
(which are just the one).
Thanks,
Brian
Cindy Swearingen wrote:
Hi Brian,
Because the pool is still online and the metadata is redundant, maybe
these errors were caused by a brief hiccup from the USB device's
physical connection. You might try:
# zpool clear external c0t0d0p0
Then, run a scrub:
# zpool scrub external
If the above fails, then please identify the Solaris release and what
events preceded this problem.
Thanks,
Cindy
On 06/29/10 11:15, W Brian Leonard wrote:
Hi Cindy,
The scrub didn't help and yes, this is an external USB device.
Thanks,
Brian
Cindy Swearingen wrote:
Hi Brian,
You might try running a scrub on this pool.
Is this an external USB device?
Thanks,
Cindy
On 06/29/10 09:16, Brian Leonard wrote:
Hi,
I have a zpool which is currently reporting that the
"<metadata>:<0x13>" file is corrupt:
bleon...@opensolaris:~$ pfexec zpool status -xv external
pool: external
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise
restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
external ONLINE 0 0 0
c0t0d0p0 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
<metadata>:<0x13>
Otherwise, as you can see, the pool is online. As it's unclear to
me how to restore the "<metadata>:<0x13>" file, is my only option
for correcting this error to destroy and recreate the pool?
Thanks,
Brian
--
W Brian Leonard
Principal Product Manager
860.206.6093
http://blogs.sun.com/observatory
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
