 |
 |
On Tue, 2005-12-06 at 17:12, Graeme Stewart wrote: > > We also have additional storage that is nfs-mounted on the pool node, > > but this does not appear neither in GStat nor in dpm-qryconf (see below > > - the mount point would be pc30 /storage/atlas). I'm not sure whether > > this is correct, but I think it isn't. I am also not sure permissions > > are set correctly, as I don't seem to be able to dpns-rm a file that I > > have just copied (this test had worked fine a few days ago). > > No, this isn't the right way to do things. DPM gets the size of the filesystem > using statfs64(), which will never see the size of things mounted beneath > that filesystem's mount point. > > What you should do is: > > 1. Unmount /storage/atlas from pc30:/storage. > 2. Change fstab to make its mount point somewhere independent > (e.g., /storage1). Re-mount it. > 3. Follow steps 7 and 9 of the http://wiki.gridpp.ac.uk/wiki/DPM_Disk_Pool > wiki article, i.e., > pc30# chmod dpmmgr: /storage1 > pc55# dpm-addfs --poolname dpmPart --server pc30 --fs /storage1 > (You don't have to do the rest bacause pc30 already is a disk pool, you're > just adding a new filesystem to this pool.) > > Then things should work. > > I assume there's no data on this filesystem....? If there is we might have to > think about this quite carefully - perhaps a soft link from /storage/atlas > to /storage1/atlas so that old lfns work through the "vanilla" gridftp > server? Something to check. There's indeed data on this filesystem. What's your advice then? cheers, gianfranco