zfs discuss - Sep 2010 - My filesystem turned from a directory into a special character device

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. Perhaps this is related?

Any ideas how to get access to my file system? 

Thanks,
-Scott
-- 
This message posted from opensolaris.org

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

On 9/27/10 9:56 AM, "Victor Latushkin" <victor.latushkin at
oracle.com> 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? 
Yes. Well, I have removed those entries in /etc/system, but have not yet
rebooted the box.
> 
>> 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.
OK. Sounds like restoring from my backup would be best?

What causes this? I saw this exact same behavior on my home box, and had to
restore about two weeks ago. Not very encouraging. :(

Is there anything I can provide to help people who know more than me solve
this problem?
> 
> Regards
> Victor
Thanks Victor.

-Scott


--------------------------------------------------------------------------------
We value your opinion!  How may we serve you better? 
Please click the survey link to tell us how we are doing:
http://www.craneae.com/ContactUs/VoiceofCustomer.aspx
Your feedback is of the utmost importance to us. Thank you for your time.
--------------------------------------------------------------------------------
Crane Aerospace & Electronics Confidentiality Statement:
The information contained in this email message may be privileged and is 
confidential information intended only for the use of the recipient, or any 
employee or agent responsible to deliver it to the intended recipient. Any 
unauthorized use, distribution or copying of this information is strictly
prohibited
and may be unlawful. If you have received this communication in error, please
notify
the sender immediately and destroy the original message and all attachments from
your electronic files.
--------------------------------------------------------------------------------

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 at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>   

-- 




-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100929/d9f0e75c/attachment.html>