Backup Central

I am hoping someone can help me here. I have a fedora 14 machine backing up to a networked WD Sharespace using rnsapshot. 

I use nfs to mount to the sharespace (raid 0 configuration) backup folder. that works fine. i can copy to the target directory on the sharespace no problem.

the intial backup with rsnapshot  works fine. on the next backup i get errors 'invalid cross-device link" errors like this "/bin/cp: cannot create link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma': Invalid cross-device link" and then it exits with this: " /bin/cp -al /mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit status 1). Perhaps your cp does not support -al options?"

I have searched around and cannot find a solution. 

any help or direction where i might find some would be great. thanks.

On Fri, Jan 13, 2012 at 08:59:55AM -0500, Charles Stanton wrote:

the intial backup with rsnapshot works fine. on the next backup i get
errors 'invalid cross-device link" errors like this "/bin/cp: cannot create
link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma':
Invalid cross-device link" and then it exits with this: " /bin/cp -al
/mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit
status 1). Perhaps your cp does not support -al options?"

There seem to be quite a few people asking about this error on NFS
volumes in different places on t'interweb, with no useful-looking
solutions suggested.

Please can you do this:

cd /mnt/netbackup
touch foo
ln foo bar

and let us know if it successfully links *any* files at all. If it
doesn't then stop there, because that means that the underlying
filesystem won't work with rsnapshot. If it *does* work, then show us
the results of:

df -i /mnt/netbackup
to see if the device has run out of inodes
stat /mnt/netbackup/daily.[01]
to see if they're really the same device

and then, if you can get a shell on the NFS server, all of those again
on the appropriate directories.

--
header FROM_DAVID_CANTRELL From =~ /david.cantrell/i
describe FROM_DAVID_CANTRELL Message is from David Cantrell
score FROM_DAVID_CANTRELL 15.72 # This figure from experimentation

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

David,   Thanks so much.  Here are the results. 

A. From machine (media-server) that runs rsnapshot:

1.  linking works.  the commands created foo and bar in  the target directory (/mnt/netbackup).

2.  the results of the df -i command:

[media-server.localdomain netbackup]# df -i /mnt/netbackup
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
192.168.1.20:/nfs/netbackup
                     976060416   65490 975994926    1% /mnt/netbackup
[media-server.localdomain netbackup]#


3.  Results of the stat command:
[media-server.localdomain netbackup]# stat /mnt/netbackup/daily.[01]
  File: `/mnt/netbackup/daily.0'
  Size: 4096            Blocks: 8          IO Block: 32768  directory
Device: 17h/23d Inode: 780107778   Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: 2012-01-12 23:16:37.000000000 -0500
Modify: 2012-01-12 23:16:37.000000000 -0500
Change: 2012-01-12 23:16:37.000000000 -0500
  File: `/mnt/netbackup/daily.1'
  Size: 4096            Blocks: 8          IO Block: 32768  directory
Device: 17h/23d Inode: 780107885   Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: 2012-01-12 23:16:37.000000000 -0500
Modify: 2012-01-12 23:16:37.000000000 -0500
Change: 2012-01-13 03:25:38.000000000 -0500
[media-server.localdomain netbackup]#

Note that the daily.1 directory has no files in it, just directories, since it gets the cross device link errors.

B. Results of the same commands run from the shell of the target machine (WD Share Space)

1. linking works.  i created boo and linked to hoo'

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md2             7685865852 1805995540 5879870312  23% /DataVolume

3.  Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
  File: "/DataVolume/netbackup/daily.0"
  Size: 836463          Blocks: 836463     IO Block: 4096   directory
Device: d95e3h/836463d  Inode: 836463      Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Thu Jan 12 23:16:37 2012
  File: "/DataVolume/netbackup/daily.1"
  Size: 836463          Blocks: 836463     IO Block: 4096   directory
Device: d95e3h/836463d  Inode: 836463      Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Fri Jan 13 03:25:38 2012

Really appreciate the help! Charles


On Fri, Jan 13, 2012 at 11:56 AM, David Cantrell <david < at > cantrell.org.uk ([email]david < at > cantrell.org.uk[/email])> wrote:
On Fri, Jan 13, 2012 at 08:59:55AM -0500, Charles Stanton wrote:

the intial backup with rsnapshot  works fine. on the next backup i get
errors 'invalid cross-device link" errors like this "/bin/cp: cannot create
link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma':
Invalid cross-device link" and then it exits with this: " /bin/cp -al
/mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit
status 1). Perhaps your cp does not support -al options?"


There seem to be quite a few people asking about this error on NFS
volumes in different places on t'interweb, with no useful-looking
solutions suggested.

Please can you do this:

cd /mnt/netbackup
touch foo
ln foo bar

and let us know if it successfully links *any* files at all.  If it
doesn't then stop there, because that means that the underlying
filesystem won't work with rsnapshot.  If it *does* work, then show us
the results of:

df -i /mnt/netbackup
 to see if the device has run out of inodes
stat /mnt/netbackup/daily.[01]
 to see if they're really the same device

and then, if you can get a shell on the NFS server, all of those again
on the appropriate directories.

--
header   FROM_DAVID_CANTRELL    From =~ /david.cantrell/i
describe FROM_DAVID_CANTRELL    Message is from David Cantrell
score    FROM_DAVID_CANTRELL    15.72 # This figure from experimentation

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Regarding this:

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 7685865852 1805995540 5879870312 23% /DataVolume


I am confused by /nfs/netbackup (in your command) vs. /DataVolume/netbackup (your working dir) vs. /DataVolume (your mountpoint for /nfs/netbackup???) vs. /mnt/netbackup (your mountpoint in the other commands).

Can you please post the output of "mount" and then explain those four directories?


Thanks,
Derek

On 01/13/2012 03:25 PM, Charles Stanton wrote: David, Thanks so much. Here are the results.

A. From machine (media-server) that runs rsnapshot:

1. linking works. the commands created foo and bar in the target directory (/mnt/netbackup).

2. the results of the df -i command:

[media-server.localdomain netbackup]# df -i /mnt/netbackup
Filesystem Inodes IUsed IFree IUse% Mounted on
192.168.1.20:/nfs/netbackup
976060416 65490 975994926 1% /mnt/netbackup
[media-server.localdomain netbackup]#


3. Results of the stat command:
[media-server.localdomain netbackup]# stat /mnt/netbackup/daily.[01]
File: `/mnt/netbackup/daily.0'
Size: 4096 Blocks: 8 IO Block: 32768 directory
Device: 17h/23d Inode: 780107778 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: 2012-01-12 23:16:37.000000000 -0500
Modify: 2012-01-12 23:16:37.000000000 -0500
Change: 2012-01-12 23:16:37.000000000 -0500
File: `/mnt/netbackup/daily.1'
Size: 4096 Blocks: 8 IO Block: 32768 directory
Device: 17h/23d Inode: 780107885 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: 2012-01-12 23:16:37.000000000 -0500
Modify: 2012-01-12 23:16:37.000000000 -0500
Change: 2012-01-13 03:25:38.000000000 -0500
[media-server.localdomain netbackup]#

Note that the daily.1 directory has no files in it, just directories, since it gets the cross device link errors.

B. Results of the same commands run from the shell of the target machine (WD Share Space)

1. linking works. i created boo and linked to hoo'

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 7685865852 1805995540 5879870312 23% /DataVolume

3. Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
File: "/DataVolume/netbackup/daily.0"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Thu Jan 12 23:16:37 2012
File: "/DataVolume/netbackup/daily.1"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Fri Jan 13 03:25:38 2012

Really appreciate the help! Charles


On Fri, Jan 13, 2012 at 11:56 AM, David Cantrell <david < at > cantrell.org.uk ([email]david < at > cantrell.org.uk[/email])> wrote:
On Fri, Jan 13, 2012 at 08:59:55AM -0500, Charles Stanton wrote:

the intial backup with rsnapshot works fine. on the next backup i get
errors 'invalid cross-device link" errors like this "/bin/cp: cannot create
link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma':
Invalid cross-device link" and then it exits with this: " /bin/cp -al
/mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit
status 1). Perhaps your cp does not support -al options?"


There seem to be quite a few people asking about this error on NFS
volumes in different places on t'interweb, with no useful-looking
solutions suggested.

Please can you do this:

cd /mnt/netbackup
touch foo
ln foo bar

and let us know if it successfully links *any* files at all. If it
doesn't then stop there, because that means that the underlying
filesystem won't work with rsnapshot. If it *does* work, then show us
the results of:

df -i /mnt/netbackup
to see if the device has run out of inodes
stat /mnt/netbackup/daily.[01]
to see if they're really the same device

and then, if you can get a shell on the NFS server, all of those again
on the appropriate directories.

--
header FROM_DAVID_CANTRELL From =~ /david.cantrell/i
describe FROM_DAVID_CANTRELL Message is from David Cantrell
score FROM_DAVID_CANTRELL 15.72 # This figure from experimentation

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss


------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2

_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

(Note: Please keep list traffic on the list. Someone with the same symptoms will google this someday and want to know what happened.)

Follow-up question: you gave the output of mount on media-server.localdomain...

[media-server.localdomain etc]# mount
[...snip...]


But then you showed the ls contents of /nfs and /DataVolume. Were those directories on the WD Sharespace?

Please provide the output of "mount" on both media-server.localdomain and also on the WD Sharespace NFS device (in the same email, for easy comparison).

I want to see this so I can understand the shell output you are pasting, and also to see if the WD Sharespace uses a Windows-based filesystem. (I don't think Windows filesystems like FAT32 or NTFS can handle hardlinks.)

When you use their web interface to create an nfs share it shows up under under DataVolume and nfs as well.

Can you please explain why the ls contents of /DataVolume and /nfs were different? /DataVolume had extra stuff like jewab, _torrent_, temp, etc.


Thanks,
Derek

On 01/13/2012 06:10 PM, Charles Stanton wrote: here it is:

[media-server.localdomain etc]# mount
/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/VolGroup02-lv_storage on /storage type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
192.168.1.20:/nfs/netbackup on /mnt/netbackup type nfs (rw,soft,intr,nfsvers=3,addr=192.168.1.20)
[media-server.localdomain etc]#

I am not clear on how WD Sharespace implements nfs, but it appears that the actual directory is DataVolumenetbackup. but there is also an nfs directroy which shows the nfs shares. When you use their web interface to create an nfs share it shows up under under DataVolume and nfs as well.

Here is the ls output

/ $ cd nfs
/nfs $ ls
Download Public netbackup
/nfs $ cd /DataVolume/

and

/ $ cd DataVolume
/DataVolume $ ls
Public aquota.user netbackup
Download _torrent_ jewab temp
/DataVolume $


and here is the root directory listing

/ $ ls
CacheVolume dev lost+found proto twonky
Configuration etc mnt root usr
DataVolume exports.sarma nfs sbin var
ExtendVolume jewab old shares
bin lib opt tmp
boot linuxrc proc trustees
/ $

thanks


On Fri, Jan 13, 2012 at 8:47 PM, Derek Simkowiak <derek < at > simkowiak.net ([email]derek < at > simkowiak.net[/email])> wrote:
Regarding this:

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 7685865852 1805995540 5879870312 23% /DataVolume



I am confused by /nfs/netbackup (in your command) vs. /DataVolume/netbackup (your working dir) vs. /DataVolume (your mountpoint for /nfs/netbackup???) vs. /mnt/netbackup (your mountpoint in the other commands).

Can you please post the output of "mount" and then explain those four directories?


Thanks,
Derek

On 01/13/2012 03:25 PM, Charles Stanton wrote: David, Thanks so much. Here are the results.

A. From machine (media-server) that runs rsnapshot:

1. linking works. the commands created foo and bar in the target directory (/mnt/netbackup).

2. the results of the df -i command:

[media-server.localdomain netbackup]# df -i /mnt/netbackup
Filesystem Inodes IUsed IFree IUse% Mounted on
192.168.1.20:/nfs/netbackup
976060416 65490 975994926 1% /mnt/netbackup
[media-server.localdomain netbackup]#


3. Results of the stat command:
[media-server.localdomain netbackup]# stat /mnt/netbackup/daily.[01]
File: `/mnt/netbackup/daily.0'
Size: 4096 Blocks: 8 IO Block: 32768 directory
Device: 17h/23d Inode: 780107778 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Modify: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Change: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
File: `/mnt/netbackup/daily.1'
Size: 4096 Blocks: 8 IO Block: 32768 directory
Device: 17h/23d Inode: 780107885 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Modify: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Change: [url=tel:2012-01-13%2003]2012-01-13 03[/url]:25:38.000000000 -0500
[media-server.localdomain netbackup]#

Note that the daily.1 directory has no files in it, just directories, since it gets the cross device link errors.

B. Results of the same commands run from the shell of the target machine (WD Share Space)

1. linking works. i created boo and linked to hoo'

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 7685865852 1805995540 5879870312 23% /DataVolume

3. Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
File: "/DataVolume/netbackup/daily.0"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Thu Jan 12 23:16:37 2012
File: "/DataVolume/netbackup/daily.1"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
Access: (0755/drwxr-xr-x) Uid: (65534/nfsnobody) Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Fri Jan 13 03:25:38 2012

Really appreciate the help! Charles


On Fri, Jan 13, 2012 at 11:56 AM, David Cantrell <david < at > cantrell.org.uk ([email]david < at > cantrell.org.uk[/email])> wrote:
On Fri, Jan 13, 2012 at 08:59:55AM -0500, Charles Stanton wrote:

the intial backup with rsnapshot works fine. on the next backup i get
errors 'invalid cross-device link" errors like this "/bin/cp: cannot create
link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma':
Invalid cross-device link" and then it exits with this: " /bin/cp -al
/mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit
status 1). Perhaps your cp does not support -al options?"


There seem to be quite a few people asking about this error on NFS
volumes in different places on t'interweb, with no useful-looking
solutions suggested.

Please can you do this:

cd /mnt/netbackup
touch foo
ln foo bar

and let us know if it successfully links *any* files at all. If it
doesn't then stop there, because that means that the underlying
filesystem won't work with rsnapshot. If it *does* work, then show us
the results of:

df -i /mnt/netbackup
to see if the device has run out of inodes
stat /mnt/netbackup/daily.[01]
to see if they're really the same device

and then, if you can get a shell on the NFS server, all of those again
on the appropriate directories.

--
header FROM_DAVID_CANTRELL From =~ /david.cantrell/i
describe FROM_DAVID_CANTRELL Message is from David Cantrell
score FROM_DAVID_CANTRELL 15.72 # This figure from experimentation

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss





------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Derek - Yes the DatabVoume and NFS directories are on the sharespace. 

 here is the output of mount on both:

Sharespace:
/ $ mount
/dev/root on /old type cramfs (ro)
proc on /old/proc type proc (rw,nodiratime)
/dev/md0 on / type ext3 (rw,noatime)
proc on /proc type proc (rw,nodiratime)
/proc/bus/usb/ on /proc/bus/usb type usbfs (rw)
/dev/pts on /dev/pts type devpts (rw)
trusteesfs on /trustees type trusteesfs (rw)
/dev/md2 on /DataVolume type ext3 (rw,noatime)
/dev/ram0 on /mnt/ram type tmpfs (rw)
/dev/md2 on /shares/Public type ext3 (rw,noatime)
/dev/md2 on /shares/Download type ext3 (rw,noatime)
/dev/md2 on /shares/netbackup type ext3 (rw,noatime)
/dev/md2 on /shares/testnfs type ext3 (rw,noatime)
/ $

on the rsnapshot media-server.local machine:

[media-server.localdomain ~]# mount
/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/VolGroup02-lv_storage on /storage type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
192.168.1.20:/DataVolume/netbackup on /mnt/netbackup type nfs (rw,soft,intr,nfsvers=3,addr=192.168.1.20)
[media-server.localdomain ~]#

On the second question, i'm not sure.  I do know that some of them - like jewab and torrent - are created by the device after formatting.  I created Backup, to test setting up an nfs share without using the web interface and got the same result.

as to hard linking to a windows ntfs share, i was using rsnapshot before backing up to windows machine and mounting using cifs and it worked well.  i ran out of space so I bought the sharespace....i did try using cifs to mount a share on the sharespace and i can create the mount point, but i got the same cross-device link error.  someone suggested that nfs was better, so i tried that. 

thanks again. 


On Sat, Jan 14, 2012 at 3:22 AM, Derek Simkowiak <derek < at > simkowiak.net ([email]derek < at > simkowiak.net[/email])> wrote:
(Note: Please keep list traffic on the list.  Someone with the same symptoms will google this someday and want to know what happened.)

    Follow-up question: you gave the output of mount on media-server.localdomain...

[media-server.localdomain etc]# mount
[...snip...]


    But then you showed the ls contents of /nfs and /DataVolume.  Were those directories on the WD Sharespace?

    Please provide the output of "mount" on both media-server.localdomain and also on the WD Sharespace NFS device (in the same email, for easy comparison).

    I want to see this so I can understand the shell output you are pasting, and also to see if the WD Sharespace uses a Windows-based filesystem.  (I don't think Windows filesystems like FAT32 or NTFS can handle hardlinks.)

When you use their web interface to create an nfs share it shows up under under DataVolume and  nfs as well.


    Can you please explain why the ls contents of /DataVolume and /nfs were different?  /DataVolume had extra stuff like jewab, _torrent_, temp, etc.


Thanks,
Derek


On 01/13/2012 06:10 PM, Charles Stanton wrote: here it is:

[media-server.localdomain etc]# mount
/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/VolGroup02-lv_storage on /storage type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
192.168.1.20:/nfs/netbackup on /mnt/netbackup type nfs (rw,soft,intr,nfsvers=3,addr=192.168.1.20)
[media-server.localdomain etc]#

I am not  clear on how WD Sharespace implements nfs, but it appears that the actual directory is DataVolumenetbackup.  but there is also an nfs directroy which shows the nfs shares.   When you use their web interface to create an nfs share it shows up under under DataVolume and  nfs as well. 

Here is the ls output

/ $ cd nfs
/nfs $ ls
Download   Public     netbackup
/nfs $ cd /DataVolume/

and

/ $ cd DataVolume
/DataVolume $ ls
Public       aquota.user  netbackup
Download     _torrent_    jewab        temp
/DataVolume $


and here is the root directory listing

/ $ ls
CacheVolume    dev            lost+found     proto          twonky
Configuration  etc            mnt            root           usr
DataVolume     exports.sarma  nfs            sbin           var
ExtendVolume   jewab          old            shares
bin            lib            opt            tmp
boot           linuxrc        proc           trustees
/ $

thanks


On Fri, Jan 13, 2012 at 8:47 PM, Derek Simkowiak <derek < at > simkowiak.net ([email]derek < at > simkowiak.net[/email])> wrote:
Regarding this:

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md2             7685865852 1805995540 5879870312  23% /DataVolume



I am confused by /nfs/netbackup (in your command) vs. /DataVolume/netbackup (your working dir) vs. /DataVolume (your mountpoint for /nfs/netbackup???) vs. /mnt/netbackup (your mountpoint in the other commands).

Can you please post the output of "mount" and then explain those four directories?


Thanks,
Derek

On 01/13/2012 03:25 PM, Charles Stanton wrote: David,   Thanks so much.  Here are the results. 

A. From machine (media-server) that runs rsnapshot:

1.  linking works.  the commands created foo and bar in  the target directory (/mnt/netbackup).

2.  the results of the df -i command:

[media-server.localdomain netbackup]# df -i /mnt/netbackup
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
192.168.1.20:/nfs/netbackup
                     976060416   65490 975994926    1% /mnt/netbackup
[media-server.localdomain netbackup]#


3.  Results of the stat command:
[media-server.localdomain netbackup]# stat /mnt/netbackup/daily.[01]
  File: `/mnt/netbackup/daily.0'
  Size: 4096            Blocks: 8          IO Block: 32768  directory
Device: 17h/23d Inode: 780107778   Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Modify: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Change: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
  File: `/mnt/netbackup/daily.1'
  Size: 4096            Blocks: 8          IO Block: 32768  directory
Device: 17h/23d Inode: 780107885   Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Modify: [url=tel:2012-01-12%2023]2012-01-12 23[/url]:16:37.000000000 -0500
Change: [url=tel:2012-01-13%2003]2012-01-13 03[/url]:25:38.000000000 -0500
[media-server.localdomain netbackup]#

Note that the daily.1 directory has no files in it, just directories, since it gets the cross device link errors.

B. Results of the same commands run from the shell of the target machine (WD Share Space)

1. linking works.  i created boo and linked to hoo'

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md2             7685865852 1805995540 5879870312  23% /DataVolume

3.  Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
  File: "/DataVolume/netbackup/daily.0"
  Size: 836463          Blocks: 836463     IO Block: 4096   directory
Device: d95e3h/836463d  Inode: 836463      Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Thu Jan 12 23:16:37 2012
  File: "/DataVolume/netbackup/daily.1"
  Size: 836463          Blocks: 836463     IO Block: 4096   directory
Device: d95e3h/836463d  Inode: 836463      Links: 3
Access: (0755/drwxr-xr-x)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: Thu Jan 12 23:16:37 2012
Modify: Thu Jan 12 23:16:37 2012
Change: Fri Jan 13 03:25:38 2012

Really appreciate the help! Charles


On Fri, Jan 13, 2012 at 11:56 AM, David Cantrell <david < at > cantrell.org.uk ([email]david < at > cantrell.org.uk[/email])> wrote:
On Fri, Jan 13, 2012 at 08:59:55AM -0500, Charles Stanton wrote:

the intial backup with rsnapshot  works fine. on the next backup i get
errors 'invalid cross-device link" errors like this "/bin/cp: cannot create
link `/mnt/netbackup/daily.1/localhost/storage/sys-files/smb.conf.sarma':
Invalid cross-device link" and then it exits with this: " /bin/cp -al
/mnt/netbackup/daily.0 /mnt/netbackup/daily.1 failed (result 256, exit
status 1). Perhaps your cp does not support -al options?"


There seem to be quite a few people asking about this error on NFS
volumes in different places on t'interweb, with no useful-looking
solutions suggested.

Please can you do this:

cd /mnt/netbackup
touch foo
ln foo bar

and let us know if it successfully links *any* files at all.  If it
doesn't then stop there, because that means that the underlying
filesystem won't work with rsnapshot.  If it *does* work, then show us
the results of:

df -i /mnt/netbackup
 to see if the device has run out of inodes
stat /mnt/netbackup/daily.[01]
 to see if they're really the same device

and then, if you can get a shell on the NFS server, all of those again
on the appropriate directories.

--
header   FROM_DAVID_CANTRELL    From =~ /david.cantrell/i
describe FROM_DAVID_CANTRELL    Message is from David Cantrell
score    FROM_DAVID_CANTRELL    15.72 # This figure from experimentation

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss





------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss








------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On Fri, Jan 13, 2012 at 06:25:14PM -0500, Charles Stanton wrote:

B. Results of the same commands run from the shell of the target machine
(WD Share Space)

1. linking works. i created boo and linked to hoo'

2. df -i command results (it did not allow the -i switch so just did df):
/DataVolume/netbackup $ df /nfs/netbackup
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 7685865852 1805995540 5879870312 23% /DataVolume

That's unfortunate, because we do need the number of spare *inodes*,
which is given by -i, not the amount of spare blokcs. Running out
of inodes while not running out of blocks can lead to some really
perverse errors.

3. Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
File: "/DataVolume/netbackup/daily.0"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
...
File: "/DataVolume/netbackup/daily.1"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3

I find this very suspicious. Both directories have the same inode, and
that's equal to their size and to the number of blocks. This indicates
that either something has gone very wrong on the filesystem, or it's a
bizarro filesystem. In particular, Unix isn't supposed to hard-link
directories, but if it has, that would explain why you can't hard link
daily.0/foo to daily.1/foo - you can't, because the link you're telling
it to create already exists on the host filesystem, because daily.0 and
daily.1 are the same directory!

In summary, you should fsck that disk and try again.

--
David Cantrell | top google result for "topless karaoke murders"

Graecum est; non legitur

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On 01/16/2012 06:48 AM, David Cantrell wrote:
3. Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
File: "/DataVolume/netbackup/daily.0"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
...
File: "/DataVolume/netbackup/daily.1"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3

I find this very suspicious. Both directories have the same inode, and
that's equal to their size and to the number of blocks. This indicates
that either something has gone very wrong on the filesystem, or it's a
bizarro filesystem.

Agreed; something weird is going on here. Here's a counter-example from one of my ext4 filesystems:

ubuntu < at > sercon-acdc:/home/rsnapshot/cst6$ stat ./daily.[01]
File: `./daily.0'
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: fc01h/64513d Inode: 49548860 Links: 25
[...snip...]
File: `./daily.1'
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: fc01h/64513d Inode: 68161456 Links: 25
[...snip...]

Notice how the inode size is 4096 (a common default). Also notice how the inodes are different, because they are two different directories. And this is what should happen when you try to hard-link two different dirs:

root < at > sercon-acdc:/# mkdir test1
root < at > sercon-acdc:/# ln ./test1 ./test2
ln: `./test1': hard link not allowed for directory

I think the problem probably has something to do with the strange way the WD Sharespace is managing the file shares. Notice how the device md2 is mounted several times. Pasted from your earlier "mount" output:

/dev/md2 on /DataVolume type ext3 (rw,noatime)
/dev/md2 on /shares/Public type ext3 (rw,noatime)
/dev/md2 on /shares/Download type ext3 (rw,noatime)
/dev/md2 on /shares/netbackup type ext3 (rw,noatime)
/dev/md2 on /shares/testnfs type ext3 (rw,noatime)

The filesystem is mounted as /DataVolume, and also as /shares/netbackup (amongst others). But you are NFS-mounting the export named /DataVolume/netbackup/. So it's unknown if that NFS export refers to md2:/ (root), md2:/DataVolume, md2:/netbackup, or md2:/DataVolume/netbackup.

My gut says this is a configuration issue and/or bug with the WD Sharespace. Perhaps the WD Sharespace GUI has a bug that messed things up. Or, it might be broken ext3 filesystem as David suggested.

If possible, I would try deleting all "shares" from the WD Sharespace. Then run "mount" and see how it's changed. Then add just a simple test-share (as an NFS export) and see if it makes more sense. Basically, you need to determine what physical filesystem (and sub-directory) your are connecting to with your NFS mount... then you can try to figure out what's wrong with that particular filesystem.

Please let us know how it goes.


Thanks,
Derek

Ok. thanks. I am going to start over - I'll delete the DataVolume raid 1 volume and re-created it (via the WD web interface.) I'll try it with what they call span (jbod)'  rather than the current raid 0 (unless you think i should try something else- the choices are raido 0, 1, 5 and 10 and the span one) and then i'll chek the output of mount on the WD. 

BTW,  It creates the Public and the Download folder shares by default - so i'm thinking it is a good idea to get the mount  output on a reformatted volume before i create any other shares or do anything else.  .

it's 7 TB so takes awhile - i'll report back tomorrow.  thanks for the help.

On Mon, Jan 16, 2012 at 7:01 PM, Derek Simkowiak <derek < at > simkowiak.net ([email]derek < at > simkowiak.net[/email])> wrote:
On 01/16/2012 06:48 AM, David Cantrell wrote:
3. Result of stat command:

/DataVolume/netbackup $ stat /nfs/netbackup/daily.[01]
File: "/DataVolume/netbackup/daily.0"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
...
File: "/DataVolume/netbackup/daily.1"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 3
I find this very suspicious. Both directories have the same inode, and
that's equal to their size and to the number of blocks. This indicates
that either something has gone very wrong on the filesystem, or it's a
bizarro filesystem.


    Agreed; something weird is going on here.  Here's a counter-example from one of my ext4 filesystems:

ubuntu < at > sercon-acdc:/home/rsnapshot/cst6$ stat ./daily.[01]
  File: `./daily.0'
  Size: 4096          Blocks: 8          IO Block: 4096   directory
Device: fc01h/64513d    Inode: 49548860    Links: 25
[...snip...]
  File: `./daily.1'
  Size: 4096          Blocks: 8          IO Block: 4096   directory
Device: fc01h/64513d    Inode: 68161456    Links: 25
[...snip...]

    Notice how the inode size is 4096 (a common default).  Also notice how the inodes are different, because they are two different directories.  And this is what should happen when you try to hard-link two different dirs:

root < at > sercon-acdc:/# mkdir test1
root < at > sercon-acdc:/# ln ./test1 ./test2
ln: `./test1': hard link not allowed for directory

    I think the problem probably has something to do with the strange way the WD Sharespace is managing the file shares.  Notice how the device md2 is mounted several times. Pasted from your earlier "mount" output:

/dev/md2 on /DataVolume type ext3 (rw,noatime)

/dev/md2 on /shares/Public type ext3 (rw,noatime)
/dev/md2 on /shares/Download type ext3 (rw,noatime)
/dev/md2 on /shares/netbackup type ext3 (rw,noatime)
/dev/md2 on /shares/testnfs type ext3 (rw,noatime)


    The filesystem is mounted as /DataVolume, and also as /shares/netbackup (amongst others).  But you are NFS-mounting the export named /DataVolume/netbackup/.  So it's unknown if that NFS export refers to md2:/ (root), md2:/DataVolume, md2:/netbackup, or md2:/DataVolume/netbackup.

    My gut says this is a configuration issue and/or bug with the WD Sharespace.  Perhaps the WD Sharespace GUI has a bug that messed things up.  Or, it might be broken ext3 filesystem as David suggested. 

    If possible, I would try deleting all "shares" from the WD Sharespace.  Then run "mount" and see how it's changed.  Then add just a simple test-share (as an NFS export) and see if it makes more sense.  Basically, you need to determine what physical filesystem (and sub-directory) your are connecting to with your NFS mount... then you can try to figure out what's wrong with that particular filesystem.

    Please let us know how it goes.


Thanks,
Derek



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Here's the output of mount and stat on the WD after reconfiguring it
as span. I have not created any shares - the ones shown are defaults.
does this help? it appears I can umount /shares/Public. but not
/shares (i get invalid argument on umount /shares)


/ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md0 2188 2188 0 100% /old
/dev/md0 202175 117377 74360 61% /
/dev/ram0 63104 64 63040 0% /mnt/ram
/dev/vg0/lv0 7685862012 141612 7685720400 0% /DataVolume
/dev/vg0/lv0 7685862012 141612 7685720400 0% /shares/Public
/ $

And


/ $ mount
/dev/root on /old type cramfs (ro)
proc on /old/proc type proc (rw,nodiratime)
/dev/md0 on / type ext3 (rw,noatime)
proc on /proc type proc (rw,nodiratime)
/proc/bus/usb/ on /proc/bus/usb type usbfs (rw)
/dev/pts on /dev/pts type devpts (rw)
trusteesfs on /trustees type trusteesfs (rw)
/dev/ram0 on /mnt/ram type tmpfs (rw)
/dev/vg0/lv0 on /DataVolume type ext3 (rw,noatime)
/dev/vg0/lv0 on /shares/Public type ext3 (rw,noatime)
/ $

stat on shares and datavolume


/ $ stat /DataVolume
File: "/DataVolume"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 7
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: Mon Jan 16 23:39:35 2012
Modify: Tue Jan 17 00:00:41 2012
Change: Tue Jan 17 00:00:41 2012
/ $

/ $ stat /shares
File: "/shares"
Size: 836463 Blocks: 836463 IO Block: 4096 directory
Device: d95e3h/836463d Inode: 836463 Links: 4
Access: (0775/drwxrwxr-x) Uid: ( 0/ root) Gid: ( 1000/ jewab)
Access: Fri Jan 13 21:23:32 2012
Modify: Mon Jan 16 23:59:47 2012
Change: Mon Jan 16 23:59:47 2012
/ $

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On Tue, Jan 17, 2012 at 10:06:33AM -0500, Charles Stanton wrote:

Here's the output of mount and stat on the WD after reconfiguring it
as span. I have not created any shares - the ones shown are defaults.
does this help? it appears I can umount /shares/Public. but not
/shares (i get invalid argument on umount /shares)


/ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md0 2188 2188 0 100% /old
/dev/md0 202175 117377 74360 61% /

That's weird. Mounting the same filesystem in two places is just Dodgy
(and I don't think it's possible on most Unixe-a-likes - but it's
sufficiently dangerous that I'm not going to try to check this!)

And

/ $ mount
/dev/root on /old type cramfs (ro)
/dev/md0 on / type ext3 (rw,noatime)

mount doesn't agree with df?!?!?

--
David Cantrell | A machine for turning tea into grumpiness

Computer Science is about lofty design goals and careful algorithmic
optimisation. Sysadminning is about cleaning up the resulting mess.

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Hallo, David,

Du meintest am 17.01.12:

/ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md0 2188 2188 0 100% /old
/dev/md0 202175 117377 74360 61% /

That's weird. Mounting the same filesystem in two places is just
Dodgy (and I don't think it's possible on most Unixe-a-likes - but
it's sufficiently dangerous that I'm not going to try to check this!)

That's possible - I've just tested it. But "df" then shows the same
informations in both lines, the only difference is the mountpoint.

In the above case the lines look like two different devices - and that's
strange.

Viele Gruesse!
Helmut

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

So the verdict is that rsnapshot won't work on the WD Sharespace?

it does appear i can link with single commands. any other suggestions?

thanks

On Tue, Jan 17, 2012 at 1:57 PM, Helmut Hullen <Hullen < at > t-online.de> wrote:
Hallo, David,

Du meintest am 17.01.12:

/ $ df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md0                  2188      2188         0 100% /old
/dev/md0                202175    117377     74360  61% /

That's weird. Mounting the same filesystem in two places is just
Dodgy (and I don't think it's possible on most Unixe-a-likes - but
it's sufficiently dangerous that I'm not going to try to check this!)

That's possible - I've just tested it. But "df" then shows the same
informations in both lines, the only difference is the mountpoint.

In the above case the lines look like two different devices - and that's
strange.

Viele Gruesse!
Helmut



------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Hallo, Charles,

Du meintest am 22.01.12:

So the verdict is that rsnapshot won't work on the WD Sharespace?

I don't know this system/machine/application/...
What kind of file system does it use?
Whar kind of OS does it use?

Viele Gruesse!
Helmut

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

helmut,

it's some WD custome linux on the WD Sharespace NAS - can't find out
what exactly the OS it uses ext3. the datavolume is a raid 0 - must
be created by mdadm. if you look at the top of the thread i am
getting cross device link errors. i am trying to use it as an nfs
share/target for rsnapshot running on Fedora 14 NAS (vortexbox). the
error is when rsnapshot runs the 2nd time. rsnapshot is running on the
Fedora box,. the first run works just fine. thanks

On Sun, Jan 22, 2012 at 11:50 AM, Helmut Hullen <Hullen < at > t-online.de> wrote:
Hallo, Charles,

Du meintest am 22.01.12:

So the verdict is that rsnapshot won't work on the WD Sharespace?

I don't know this system/machine/application/...
What kind of file system does it use?
Whar kind of OS does it use?

Viele Gruesse!
Helmut

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss