On Fri, Jul 23, 2010 at 2:14 PM, Richard Elling <rich...@nexenta.com> wrote:
> On Jul 23, 2010, at 9:10 AM, Ruslan Sivak wrote: > > > > > > # zfs umount data/rt > > #ls -lahs > > ... > > 2.0K drwxr-xr-x 2 root root 2 Jul 22 16:48 rt > > 2.0K srwxr-xr-x 17 root root 17 Jul 21 17:43 rt2 > > If at this point data/rt is unmounted, then: > mv rt2 rt2-bad > zfs mount data/rt > > > -- richard > > rt2 is actually a copy that i created from a snapshot (unfortunatelly taken after the issue started). I have already tried deleting the folder and mounting again. No luck. The issue is still there. #ls -lahs ... 2.0K sr-xr-xr-x 17 root root 17 Jul 21 17:43 rt ... # zfs umount data/rt #ls -lahs ... 2.0K drwxr-xr-x 2 root root 2 Jul 22 16:48 rt ... # mv rt rt.bad # ls -lahs ... 2.0K drwxr-xr-x 2 root root 2 Jul 22 16:48 rt.bad ... # zfs mount data/rt 2.0K sr-xr-xr-x 17 root root 17 Jul 21 17:43 rt So it's the volume itself thats shomehow corrupted. I was having some issues with the volume before the upgrade and I remember seeing some issue about duplicate permissions. I have also used chmod and chown to try to fix up some of the issues I was having, and could've used them with the wrong options. I dont' see how it could've caused this though. Is it possible the duplicate permissions are causing issues on this volume? Is there a way to clear that? Russ
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
