I've posted a post-mortem followup thread:
http://opensolaris.org/jive/thread.jspa?threadID=133472
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-disc
Thanks for the response Victor. It is certainly still relevant in the sense
that I am hoping to recover the data (although I've been informed the odds
are strongly against me)
My understanding is that Nexenta has been backporting ZFS code changes post
134. I suppose that it could be an error the
Hi Brian,
is it still relevant?
On 02.08.10 21:07, Brian Merrell wrote:
Cindy,
Thanks for the quick response. Consulting ZFS history I note the
following actions:
"imported" my three disk raid-z pool originally created on the most
"recent" version of OpenSolaris but now running NexantaSto
Cindy,
Thanks for the quick response. Consulting ZFS history I note the following
actions:
"imported" my three disk raid-z pool originally created on the most "recent"
version of OpenSolaris but now running NexantaStor 3.03
"upgraded" my pool
"destroyed" two file systems I was no longer using (n
Hi Brian,
I don't think data corruption occurs cleanly within a
file system boundary.
What kind of permission changes?
This looks like the mode/permissions of this file system
are messed up but something much worse happened.
Thanks,
Cindy
On 08/02/10 11:07, Brian Merrell wrote:
Cindy,
Th
Brian,
You might try using zpool history -il to see what ZFS operations,
if any, might have lead up to this problem.
If zpool history doesn't provide any clues, then what other
operations might have occurred prior to this state?
It looks like something trappled this file system...
Thanks,
Cin
Thanks Preston. I am actually using ZFS locally, connected directly to 3 sata
drives in a raid-z pool. The filesystem is ZFS and it mounts without complaint
and the pool is clean. I am at a loss as to what is happening.
-brian
--
This message posted from opensolaris.org
_
On Mon, 2010-08-02 at 08:48 -0700, Brian wrote:
> I have several filesystems in a raid-z pool. All seem to be working
> correctly except one which is mounted but yields the following with ls -lh:
>
> ?- ? ?? ? ? media
>
> I just finished scrubbing the pool and
I have several filesystems in a raid-z pool. All seem to be working correctly
except one which is mounted but yields the following with ls -lh:
?- ? ?? ? ? media
I just finished scrubbing the pool and there are no errors. I can't seem to do
anything with the
