Igor,

I meant to reply to the group to let them know that the problem had been solved, but your email makes me think that it has not been solved fully. The script runs as user backuppc and apparently user backuppc did not have permission to write to the data locations. Once I fixed the permissions issue, the command start stop command would work and give me an "ok."

What makes me think that the problem has not been solved fully is that when I run the first two of your commands, I get no response (as expected) and the testgram is created properly. However, your third command does gives me an error that I don't understand. Below are the results:

backuppc@linux-pc5:/data/BackupPC/pc$ touch /data/BackupPC/pc/testgram
backuppc@linux-pc5:/data/BackupPC/pc$

backuppc@linux-pc5:/$ ln /data/BackupPC/pc/testgram /data/BackupPC/cpool
backuppc@linux-pc5:/$

backuppc@linux-pc5:/$ rm /data/BackupPC/pc/testgram /data/BackupPC/cpool
rm: cannot remove ‘/data/BackupPC/cpool’: Is a directory

Is the output what was to be expected? A couple of things are throwing me for a loop. First, on the remove command "rm /data/BackupPC/pc/testgram /data/BackupPC/cpool", should that really be "rm /data/BackupPC/pc/testgram /data/BackupPC/cpool/testgram" and is that the nature of the Is a directory error? I presume so. Or should my merely removing the linked target also remove the linked file?

Second, the "could not find valid filesystem superblock error is unclear.