Currently, you have only one solution repair xfs.
Note: you should read this topic about xfs_repair which requires more ressource to run:
http://plugout.net/viewtopic.php?f=26&t=2247&p=19210&hilit=console+swap#p19210
# cp -a /mountpoint/shares/2/\(1\)\ SAMSUNG\ HD103SI1AG01118\ -S1VSJD2Z907470.dsk /mountpoint2
/Vol-B/
cp: can't open '/mountpoint/shares/2/(1) SAMSUNG HD103SI1AG01118 -S1VSJD2Z907470.dsk': File too large
# mount
rootfs on / type rootfs (rw,size=255008k,nr_inodes=63752)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sdd8 on /mountpoint2 type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
/dev/md4 on /mountpoint type xfs (ro,relatime,attr2,inode64,sunit=1024,swidth=4096,noquota)
ssh root@nas "tar cf - /path/to/directory/*" > directory.tar
cd /path/to/directory
nc -l 9999 | tar xf -
cd /path/to/directory
tar cf - * | nc ip-of-other-box 9999
I don't understand the question. Dropbear *is* an ssh server.AlexStanica wrote:Just for the sake of it, how would I use dropbear to get ssh in the standalone kernel?
cd /path/to/directory
nc -l 9999 | tar xf -
cd /path/to/directory
tar cf - * | nc ip-of-other-box 9999
I don't understand the question. Dropbear *is* an ssh server.AlexStanica wrote:Just for the sake of it, how would I use dropbear to get ssh in the standalone kernel?
Return to Lacie 5big Network vs2
Users browsing this forum: No registered users and 11 guests