You would look for the device name that might be a problem, like this:
# fmdump -eV | grep c2t4d0
vdev_path = /dev/dsk/c2t4d0s0
vdev_path = /dev/dsk/c2t4d0s0
vdev_path = /dev/dsk/c2t4d0s0
vdev_path = /dev/dsk/c2t4d0s0
Then, review the file more closely for the details of these errors,
such as th
I ran fmdump -eV > dump.txt, and opened the 64 MB text file. What should I be
looking for?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Because this is a non-redundant root pool, you should still
check fmdump -eV to make sure the corrupted files aren't
due to some ongoing disk problems.
cs
On 08/04/10 13:45, valrh...@gmail.com wrote:
Oooh... Good call!
I scrubbed the pool twice, then it showed a real filename from an old snaps
Oooh... Good call!
I scrubbed the pool twice, then it showed a real filename from an old snapshot
that I had attempted to delete before (like a month ago), and gave an error,
which I subsequently forgot about. I deleted the snapshot and cleaned up a few
other snaphots, cleared the error, rescru
Maybe it is a temporary file.
You might try running a scrub to see if it goes away.
I would also use fmdump -eV to see if this disk is
having problems.
Thanks,
Cindy
On 08/04/10 01:05, valrh...@gmail.com wrote:
I have one corrupt file in my rpool, but when I run "zpool status -v", I don't
g
I have one corrupt file in my rpool, but when I run "zpool status -v", I don't
get a filename, just an address. Any idea how to fix this? Here's the output:
p...@dellt7500:~# zpool status -v rpool
pool: rpool
state: ONLINE
status: One or more devices has experienced an error resulting in data
