On 29.06.09 23:01, Carsten Aulbert wrote:
One question:
Where can I find more about CR 6827199? I logged into sun.com with my
service contract enabled log-in but I cannot find it there (or the
search function does not like me too much).
You can try bugs.opensolaris.org too:
http://bugs.openso
Hi Mark,
Mark J Musante wrote:
>
> OK, looks like you're running into CR 6827199.
>
> There's a workaround for that as well. After the zpool import, manually
> zfs umount all the datasets under /atlashome/BACKUP. Once you've done
> that, the BACKUP directory will still be there. Manually moun
On Mon, 29 Jun 2009, Carsten Aulbert wrote:
s11 console login: root
Password:
Last login: Mon Jun 29 10:37:47 on console
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
s11:~# zpool export atlashome
s11:~# ls -l /atlashome
/atlashome: No such file or directory
s11:~# zpool import at
Hi
Mark J Musante wrote:
>
> Do a zpool export first, and then check to see what's in /atlashome. My
> bet is that the BACKUP directory is still there. If so, do an rmdir on
> /atlashome/BACKUP and then try the import again.
Sorry, I meant to copy this earlier:
s11 console login: root
Passwor
On Mon, 29 Jun 2009, Carsten Aulbert wrote:
Is there any way to force zpool import to re-order that? I could delete
all stuff under BACKUP, however given the size I don't really want to.
Do a zpool export first, and then check to see what's in /atlashome. My
bet is that the BACKUP directory
Hi
a small addendum. It seems that all sub ZFS below /atlashome/BACKUP are
already mounted when /atlashome/BACKUP is tried to be mounted:
# zfs get all atlashome/BACKUP|head -15
NAME PROPERTY VALUE SOURCE
atlashome/BACKUP type filesystem
What does 'zfs list -o name,mountpoint' and 'zfs mount' show after the
import? My only guess is that you have some explicit mountpoint set
that's confusing the DSl-orderered mounting code. If this is the case,
this was fixed in build 46 (likely to be in S10u4) to always mount
datasets in mountpoi
Robert,
Are you sure that nfs-s5-p0/d5110 and nfs-s5-p0/d5111 are mounted
following the import? These messages imply that the d5110 and d5111
directories in the top-level filesystem of pool nfs-s5-p0 are not
empty. Could you verify that 'df /nfs-s5-p0/d5110' displays
nfs-s5-p0/d5110 as the "Fil
