Re: [zfs-discuss] How to get nfs work with zfs?

2011-12-06 Thread Didier Rebeix
Le Tue, 6 Dec 2011 12:52:02 +0800,
darkblue darkblue2...@gmail.com a écrit :

 I am going to share a dir and it's subdir through NFS to Virtual Host,
 which include XEN(CentOS/netbsd) and ESXi,but failed, the following
 step is what I did:
 
 solaris 11:
 
  zfs create tank/iso
  zfs create tank/iso/linux
  zfs create tank/iso/windows
 
  share -F nfs -o rw,nosuid,root=VM-host1:VM-host2 /tank/iso
  chmod -R 777 /tank/iso
 
 
 centos:
 
  mkdir /home/iso
  mount -t nfs -o rw,nosuid solaris11:/tank/iso /home/iso
 
 
 echo newfile  /home/iso/newfile.txt
 success
 
 echo newfile  /home/iso/linux/newfile.txt
 failed,and display: permission denied
 
 and the, check the dir on solaris11:
 
  ls -al /tank/iso
 
  drwxrwxrwx   5 root root   8 Dec  5 13:04 .
  drwxr-xr-x   4 root root   4 Dec  2 22:45 ..
  drwxrwxrwx   2 root root   2 Dec  2 16:54 bsd
  drwxrwxrwx   2 root root   2 Dec  2 16:54 linux
  -rw-r--r--   1 nobody   nobody 8 Dec  5 12:57
  newfile.txt drwxrwxrwx   2 root root   2 Dec  2 16:54
  windows
 
 
 check the dir on CentOS:
 
  ls -al /home/iso
 
  drwxr-xr-x+ 2 root  root   2 Dec  2 16:54 bsd
  drwxr-xr-x+ 2 root  root   2 Dec  2 16:54 linux
  -rw-r--r--+ 1 nfsnobody nfsnobody  8 Dec  5 12:57
  newfile.txt drwxr-xr-x+ 2 root  root   2 Dec  2
  16:54 windows
 
 
 I got couple questions:
 1、why the owner of newfile.txt is nfsnobody on CentOS, and on
 solaris, it's  nobody?
nfsnobody has the same UID on Centos as nobody has on Solaris. Check
your /etc/passwd files on both systems.
Filesystems store UIDs not login names. UIDs are resolved to login
names by tools like 'ls' by querying the system's user database which is
usualy backed by /etc/passwd.

 2、why the subdir do not have write access, how to accomplish it;
Your subdirs are in fact filesystem mount points. When exporting a
filesystem containing submounted filesystems, clients do not see them.
Clients have to mount each submount to access them. With NFS you export
a filesystem, not a hierarchy of filesystems.

 3、what does + mean?
It means ACLs are enabled. Use noacl mount option to disable.

 4、do I need to remount a share dir after changing the file access on
 solaris(NFS server)?
If you mean like chmod'ing on the server, then you don't have to
remount on the clients. 

Cheers.

-- 
Didier REBEIX
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


[zfs-discuss] zpool scrub bad block list

2011-11-08 Thread Didier Rebeix
Hi list,

from ZFS documentation it appears unclear to me if a zpool
scrub will black list any found bad blocks so they won't be used
anymore.

I know Netapp's WAFL scrub does reallocate bad blocks and mark them as
unsable. Does ZFS have this kind of strategy ?

Thanks.

-- 
Didier
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] zpool scrub bad block list

2011-11-08 Thread Didier Rebeix
Very interesting... I didn't know disk firwares were responsible for
automagically relocating bad blocks. Knowing this, it makes no sense for
a filesystem to try to deal with this kind of errors.

For now, any disk with read/write errors detected will be discarded
from my filers and replaced...

Thanks !

Le Tue, 08 Nov 2011 13:03:57 +,
Andrew Gabriel andrew.gabr...@oracle.com a écrit :

 ZFS detects far more errors that traditional filesystems will simply
 miss. This means that many of the possible causes for those errors
 will be something other than a real bad block on the disk. As Edward
 said, the disk firmware should automatically remap real bad blocks,
 so if ZFS did that too, we'd not use the remapped block, which is
 probably fine. For other errors, there's nothing wrong with the real
 block on the disk - it's going to be firmware, driver, cache
 corruption, or something else, so blacklisting the block will not
 solve the issue. Also, with some types of disk (SSD), block numbers
 are moved around to achieve wear leveling, so blacklistinng a block
 number won't stop you reusing that real block.
 


-- 
Didier REBEIX
Universite de Bourgogne
Direction des Systèmes d'Information
BP 27877
21078 Dijon Cedex
Tel: +33 380395205


___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss