Note that for slave pfs, if you are to newly create one by pfs-slave, you can not either cd, stat or mount it until you once sync with a master.
This is because a slave doesn't have a root inode (root directory) right after initialization. It does have a pfs meta data that identifies the existence of the slave pfs (@@0x00000... thing you see on readlink(2)), but it's different from that slave filesystem being mountable. # hammer pfs-slave slave > /dev/null # file ./slave/ ./slave/: cannot open `./slave/' (No such file or directory) # cd ./slave/ cd: no such file or directory: ./slave/ # mount_null ./slave /mnt mount_null: /HAMMER/@@0x0000000000000001:00002: No such file or directory # hammer pfs-update slave shared-uuid=337aa2d9-ea95-11e4-9a6a-75d435a9db68 > /dev/null # hammer mirror-copy ./master ./slave Prescan to break up bulk transfer Prescan 1 chunks, total 0 MBytes (208) Mirror-read ./master succeeded # file ./slave/ ./slave/: directory # cd ./slave/ # cd .. # mount_null ./slave /mnt # mount | grep /mnt /HAMMER/@@0x00000001000080e0:00002 on /mnt (null) 2015-04-21 21:42 GMT+09:00 <[email protected]>: > I create a hammer slave with "hammer -v mirror-stream /pfs/master > /pfs/slave" > Is it necessary to create a softlink "ln -s /pfs/slave /somewhere" or > mountpoint "mount_null /pfs/slave /mnt/slave" to access the hammer slave? > Or can i directly access the hammer slave with "cd /pfs/slave"? > > What about the master? The same questions as above. > > (Sorry for my incredibly bad english) > >
