Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've just bought a NAS, and wanted to backup my linux server to it and after much fiddling around I've succeeded with that. Along the way I tried all sorts of different things and I don't understand if I've done something wrong or not.
As a result of trying to mount the NAS disk, a directory has been created on my linux machine, like this:-
/home/<my username>/.gfs on W.X.Y.Z
(where W.X.Y.Z is the IP address of the NAS)
Is this the normal result of mount?
Also, should there be files within that directory? (I see them being copied from there when using rsync)
/dev/mapper/vg_nrg2011-lv_root on / type ext4 (rw) [_Fedora-14-i686-]
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/vg_nrg2011-lv_home on /home type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
I've no idea what sudo is?
The NAS is formatted as ext4 - tho I'm not sure if that's of any relevance, because the 'rouge directory' (if it is that) has been created on the linux server, and then is copied by rsync to the NAS (which says to me it must be a physical directory and not a mount point. But then again I don't understand mount so perhaps I've drawn a wrong conclusion).
Last edited by OliverSarmy; 08-22-2012 at 03:18 AM.
The NAS is formatted as ext4 - tho I'm not sure if that's of any relevance, because the 'rouge directory' (if it is that) has been created on the linux server, and then is copied by rsync to the NAS (which says to me it must be a physical directory and not a mount point. But then again I don't understand mount so perhaps I've drawn a wrong conclusion).
Judging by your fdisk -l output my estimation is your NAS isn't mounted. Rsync is a client-server solution, no disk mounting done by rsync.
Presumably the NAS device has some way to share it's storage either through NFS, iSCSI, SAMBA share. What method does your NAS device support? (ex. NFS)
Judging by your fdisk -l output my estimation is your NAS isn't mounted. Rsync is a client-server solution, no disk mounting done by rsync.
Presumably the NAS device has some way to share it's storage either through NFS, iSCSI, SAMBA share. What method does your NAS device support? (ex. NFS)
Yes, I know my NAS isn't mounted. And yes, I (now) know that rsync doesn't require a remote disk mounting outside of rsync. And nothing of my NAS set-up is relevant for the question I'm wanting an answer to.
(On my linux server; not my NAS) I'm wanting to know what the directory ...
/home/<my username>/.gfs on W.X.Y.Z:
(where W.X.Y.Z is the IP address of the NAS)
...is. And I'm wanting to know if it's safe to remove, and how I can remove it as...
rm -rf "./home/<my username>/.gfs on W.X.Y.Z:"
... doesn't succeed in removing it.
Last edited by OliverSarmy; 08-23-2012 at 02:08 AM.
because I'm aware I messed up, and I'm aware that the directory has more than 50GB of data within it that shouldn't be there - and I want to put right what I messed up.
Quote:
Originally Posted by mpapet
Ok,
Try this then. Is there anything in the directory now? Who owns the directory? ex. ls -lh ./whatever
Yes, there's lots of stuff in the directory - I see it being transfered to my NAS when I do an rsync of '/home/' to my NAS (I haven't as yet finished an rsync [I keep cancelling it] because of that data being there).
The owner is <my username> (the same username that is within "/home/<my username>/.gfs on W.X.Y.Z:").
If I try to move into that directory to try and see its contents with "cd "/home/<my username>/.gfs on W.X.Y.Z:" " it says no such file or directory.
(I'm away for a few days now. I'll pick up on this on Monday or Tuesday).
If I try to move into that directory to try and see its contents with "cd "/home/<my username>/.gfs on W.X.Y.Z:" " it says no such file or directory.
1. You didn't mess up.
2. if you are on the command line, the cd stanza would be "cd /home/<my username>/.gfs\ on\ W.X.Y.Z\:" no quotes. You should be able to do "cd .gfs<tab>" and then auto-complete should escape it out for you.
3. Are you using rsync on the command line or a gui-helper app? Or maybe an rsync-like application? If it's rsync proper, then I'd let rsync run to conclusion and see what happens. What's the worst that could happen? A home partition gets full and the OS keeps running. No big deal.
I don't ever recall having this issue and I use rsync for biiiig jobs from one near-full expensive array to other storage. The way I do it is mount the remote storage locally, then use the path to that device instead of rsync's server though.
3. As I'm actually successfully using rsync now, on the command line. But I tried a variety of GUI interfaces to it, all without success (their failure was probably my doing).
I've just started rsync running now, so that it works thru that rouge directory. And yep, the worst that could happen is a full disk - which is the last thing I'm wanting, seeing as this new NAS is cos I was filling the disk with my previous (and not-adequate) backup regime.
I guess you don't recall having this issue cos you're not a linux numptie like me who doesn't know what he's doing with rsync, mount, and lots of other stuff .... and while I'm a linux numptie, I've worked with computers long enough to know that I messed up and created this as a real directory on my linux machine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.