Interesting thread. So how would you go about fixing this?
I suspect you have to track down the vnode, znode_t and eventually
modify one kernel buffers for znode_phys_t. If your left with the
decision to completely rebuild then repairing this might be the only
choice some people may have.
Dave
On 09/27/10 11:56, Victor Latushkin wrote:
On Sep 27, 2010, at 8:30 PM, Scott Meilicke wrote:
I am running nexenta CE 3.0.3.
I have a file system that at some point in the last week went from a directory
per 'ls -l' to a special character device. This results in not being able to
get into the file system. Here is my file system, scott2, along with a new file
system I just created, as seen by ls -l:
drwxr-xr-x 4 root root 4 Sep 27 09:14 scott
crwxr-xr-x 9 root root 0, 0 Sep 20 11:51 scott2
Notice the 'c' vs. 'd' at the beginning of the permissions list. I had been
fiddling with permissions last week, then had problems with a kernel panic.
Are you still running with aok/zfs_recover being set? Have you seen this issue before panic?
Perhaps this is related?
May be.
Any ideas how to get access to my file system?
This can be fixed, but it is a bit more complicated and error prone that
setting couple of variables.
Regards
Victor
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
--
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
