Keeping /home/ on the NAS?

I have a desktop machine (OpenSUSE) and a NAS (Debian).

I’m trying to simplify my storage and am considering moving my SUSE desktop’s /home/* directory onto my NAS and mounting that as a samba share in SUSE.

Would this work?

On 2012-02-17 21:16, asktoby wrote:
>
> I have a desktop machine (OpenSUSE) and a NAS (Debian).
>
> I’m trying to simplify my storage and am considering moving my SUSE
> desktop’s /home/* directory onto my NAS and mounting that as a samba
> share in SUSE.
>
> Would this work?

I think not. or not correctly.
You would not have linux type permissions and symlink.
It would work over NFS.

The NAS being debian, it either has NFS already or you can set it up.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Carlos E. R. wrote:
> On 2012-02-17 21:16, asktoby wrote:
>> I have a desktop machine (OpenSUSE) and a NAS (Debian).
>>
>> I’m trying to simplify my storage and am considering moving my SUSE
>> desktop’s /home/* directory onto my NAS and mounting that as a samba
>> share in SUSE.
>>
>> Would this work?
>
> I think not. or not correctly.
> You would not have linux type permissions and symlink.
> It would work over NFS.

I don’t know about samba but I do know about NFS. My home directory is
kept on a network server and used via NFS. I used to do it the obvious
way by mounting server:/home/me onto my-computer:/home/me but I don’t do
that any longer because its a pain. There are a few problems:

(1) If the server or network are down for any reason, you can’t login to
diagnose the problem or do anything else. (there are workarounds of course)

(2) If you log in from multiple clients, or keep multiple OS or OS
versions on one client, you will have all sorts of complications from
shared profiles and other .dot files.

So what I do now is keep my home as a local directory on the client
machine. I mount server:/home onto my-computer:/home and I symlink from
my home directory to the top-level subdirectories in my network home.

Really useful info, thanks both.
I’ve got nfs working now between the server and client. Very simple to configure compared to Samba!

djh-novell, If I understand you correctly, your file system looks something like this:


[Server]
/
└── home (on local disk, served over nfs)
       └── djh (on local disk)
             ├── Photos (on local disk)
             ├── Videos (on local disk)
             └── Documents (on local disk)

[Client]
/
└── home (on local disk)
       ├── djh (on local disk)
       │     ├── Photos (symlink to /home/nfs_mount/Photos)
       │     ├── Videos (symlink to /home/nfs_mount/Videos)
       │     └── Documents (symlink to /home/nfs_mount/Documents)
       └── nfs_mount
              ├── Photos
              ├── Videos
              └── Documents

Am I anywhere near close with that?

asktoby wrote:
> djh-novell, If I understand you correctly, your file system looks
> something like this:

That’s basically right. nfs_mount is actually a separate part of the
root tree, rather than part of /home, like this:

(caution, I use NNTP, so apologies if the ASCII art comes out wrong on
the web)

> Code:
> --------------------
>
> [Server]
> /
> └── home (on local disk, served over nfs)
| └── djh (on local disk)
| and symlinks as for client
|— nfs
|- home
|- djh
├── Photos (on local disk)
├── Videos (on local disk)
└── Documents (on local disk)
>
> [Client]
> /
> └── home (on local disk)
> ├── djh (on local disk)
> │ ├── Photos (symlink to /nfs/home/djh/Photos)
> │ ├── Videos (symlink to /nfs/home/djh/Videos)
> │ └── Documents (symlink to /nfs/home/djh/Documents)
> └── nfs
|- home (nfs mount of server:/nfs/home)
>
> --------------------

On 2012-02-24, Dave Howorth <djh-novell@no-mx.forums.opensuse.org> wrote:
> asktoby wrote:
>> djh-novell, If I understand you correctly, your file system looks
>> something like this:
>
> That’s basically right. nfs_mount is actually a separate part of the
> root tree, rather than part of /home, like this:
>
> (caution, I use NNTP, so apologies if the ASCII art comes out wrong on
> the web)
>
>> Code:
>> --------------------
>>
>> [Server]
>> /
>> └── home (on local disk, served over nfs)
> | └── djh (on local disk)
> | and symlinks as for client
> |— nfs
> |- home
> |- djh
> ├── Photos (on local disk)
> ├── Videos (on local disk)
> └── Documents (on local disk)
>>
>> [Client]
>> /
>> └── home (on local disk)
>> ├── djh (on local disk)
>> │ ├── Photos (symlink to /nfs/home/djh/Photos)
>> │ ├── Videos (symlink to /nfs/home/djh/Videos)
>> │ └── Documents (symlink to /nfs/home/djh/Documents)
>> └── nfs
> |- home (nfs mount of server:/nfs/home)

The ASCII came out wrong but, never fear, I just booted my newsreader.
Had no idea these forums were browseable via NNTP! :slight_smile:

I think I understand what you’ve done, and will model mine similarly.
Thanks for the tips.


-Toby
Add the word afiduluminag to the subject to circumvent my email filters.

On 2012-02-24 17:49, Dave Howorth wrote:

> (caution, I use NNTP, so apologies if the ASCII art comes out wrong on
> the web)

You can also use code tags via NNTP. I do.


>>
>>   [Client]
>>   /
>>   └── home (on local disk)
>>          ├── djh (on local disk)
>>   │      ├── Photos (symlink to /nfs/home/djh/Photos)

I would use:


└── home (on local disk)
├── djh (on local disk)
└─ Photos (symlink to /nfs/home/djh/Photos)

Ie, “photos” a symlink inside "/home/user/


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)