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.
On 9/27/10 9:56 AM, "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
>> b
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 sy
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
