Forum: 4WheelHam BBS

NFS File Area Issue

From paulie420@1337:3/129 to All on Mon Mar 22 19:37:33 2021

I'm gonna post this on tqwNet first, to see if anyone might have run into this issue...

So I have a very basic NAS system, running on a Raspberry Pi 3 board. Its not fast, its not HUGE, but it works for me and has been serving me well.

I have a really large collection of ROMs on this NAS, so I mounted an NFS drive

to my bbs box. It goes to /mnt/Backup4TB and has folders off of that directory.

I added all the file areas, uploaded the files and everything went as normal as

any other drive/file areas.

I set them, first, as 'slow media' which I knew would copy the files over to the BBS box first, before users could download. When users try to download, they get one of those fairly regular Z-errors on download. (I don't remember the exact error, but one that says 'receieved Z-Something instead of '...)

So then I thought maybe I'll turn off 'slow media' and see if it fixed anything. It didn't. Am I missed something? If something more needed, to use an

NFS drive? I just used a simple 'mount -t nfs' command, and the HDD mounts like

normal. The BBS box 'thinks' its just another directory - but maybe I don't know something I'm missing.

Thanks for any help; we should be able to use these types of mounts for file areas, right?

Hmmmmm...

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

From deon@1337:2/101 to paulie420 on Wed Mar 24 00:02:52 2021

Re: NFS File Area Issue
By: paulie420 to All on Mon Mar 22 2021 07:37 pm

Hey Paulie,

Thanks for any help; we should be able to use these types of mounts for

file areas, right?

I dont really understand the error might be helpeful to get the actual error - but to answer your question - yes.

My fileareas are an NFS mount, although I havent tried downloads - but I dont think it should be an issue.

...��

... The happiest time of anyone's life is just after the first divorce.
--- SBBSecho 3.13-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

From MeaTLoTioN@1337:1/101 to deon on Tue Mar 23 14:32:03 2021

On 24 Mar 2021, deon said the following...

Re: NFS File Area Issue
By: paulie420 to All on Mon Mar 22 2021 07:37 pm

Hey Paulie,

Thanks for any help; we should be able to use these types of mounts f file areas, right?

I dont really understand the error might be helpeful to get the actual error -but to answer your question - yes.

My fileareas are an NFS mount, although I havent tried downloads - but I dontthink it should be an issue.

Yes, you can use NFS mounts for your file areas, I have a bunch on
mine. Also you can use symlinks and bind mounts too. As long as the FS
can be seen from the normal navigation and mystic has read/write access
to the areas, it should be all gravy.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07�� |08[|10eml|08] |15ml@erb.pw |07�� |08[|10web|08] |15www.erb.pw |07��Ŀ |07�� |08[|09fsx|08] |1521:1/158 |07�� |08[|11tqw|08] |151337:1/101 |07�� |07�� |08[|12rtn|08] |1580:774/81 |07�� |08[|14fdn|08] |152:250/5 |07��
|07�� |08[|10ark|08] |1510:104/2 |07��

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

From paulie420@1337:3/129 to deon on Wed Mar 24 09:25:44 2021

Thanks for any help; we should be able to use these types of mounts f file areas, right?

I dont really understand the error might be helpeful to get the actual error - but to answer your question - yes.
...��

Yes, you can use NFS mounts for your file areas, I have a bunch on
mine. Also you can use symlinks and bind mounts too. As long as the FS
can be seen from the normal navigation and mystic has read/write access
to the areas, it should be all gravy.
MeaTLoTioN

Thanks for replying deon.. also, I posted mL's response and I feel pretty stupid. So yea, thats it - it must be the permissions. Derp.

mL has recently seen some of my knowledge with Linux; I know a lot, and then.. I know so little. Even I should have known this... I didn't give ANY access consideration to the NFS drive. So thats most likely where Mystic is failing.

My BBS is on user 'pi'... and my NAS is on a user 'paulie420'. Lol, the /ROMs folder is listed 'paulie420 : users'. And I suppose I'm gonna need a whole lesson on permissions - which I can do mostly on my own time, but...

On my local BBS box I know how to use chown and chmod to make sure Mystic has access to things it needs. But on this NFS mount, is it going to be that I need

to add the BBS box credentials to that 'users' group?

Again, I can learn how to doso on my own time, but... in what way do I give the

BBS box access to the remote NAS /ROMs folder?

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

From deon@1337:2/101 to paulie420 on Thu Mar 25 09:40:58 2021

Re: Re: NFS File Area Issue
By: paulie420 to deon on Wed Mar 24 2021 09:25 am

Howdy,

mL has recently seen some of my knowledge with Linux; I know a lot, and

then.. I know so little. Even I should have known this... I didn't give ANY access consideration to the NFS drive. So thats most likely where Mystic is failing.

My BBS is on user 'pi'... and my NAS is on a user 'paulie420'. Lol, the

/ROMs folder is listed 'paulie420 : users'. And I suppose I'm gonna need a whole lesson on permissions - which I can do mostly on my own time, but...

So cross device NFS is a pain...

At the end of the day, file access talks UID/GID (numbers) - just like DNS names resolve to an IP address so 2 things can talk to each other.

On all my systems, my user is "deon", which is always the same UID (say 2000), and my "users" also has the same GID (say 1000). Then when I save a file as deon:users on any system - if that system exports a filesystem via NFS, any other system I can still access it (because deon:users = 2000:1000).

So if you are sharing stuff to your PI - and the files are owned paulie420:users, and the Pi application is running as pi:users - while "paulie420" and "pi" can have different UIDs - your users group should have the

same GID. Then if you files and dirs have g=rwx (then your "pi:users" user can read your files on the NAS that are owned by paulie420:users).

(Its perfectly legal that the UID for "pi" and "paulie420" be the same number, then u=rwx would apply.)

IE: It doesnt matter what the text is for a user or a group (that's for us humans), its the IDs that they map to that is important for access control.

Now, if you doing stuff as "root", then there is a different issue to address -

since NFS can map root to "nobody" if nfs_root_squash is used (its a protective

thing, but it can trip you up every now and again).

...��

... Deny thy father and forget thy tagline.
--- SBBSecho 3.13-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

From MeaTLoTioN@1337:1/101 to deon on Thu Mar 25 00:44:39 2021

On 25 Mar 2021, deon said the following...

Re: Re: NFS File Area Issue
By: paulie420 to deon on Wed Mar 24 2021 09:25 am

Howdy,

mL has recently seen some of my knowledge with Linux; I know a lot, a

then.. I know so little. Even I should have known this... I didn't give ANY access consideration to the NFS drive. So thats most likely where Mystic is failing.

My BBS is on user 'pi'... and my NAS is on a user 'paulie420'. Lol, t

/ROMs folder is listed 'paulie420 : users'. And I suppose I'm gonna
need a whole lesson on permissions - which I can do mostly on my own
time, but...

So cross device NFS is a pain...

At the end of the day, file access talks UID/GID (numbers) - just like
DNS names resolve to an IP address so 2 things can talk to each other.

On all my systems, my user is "deon", which is always the same UID (say 2000), and my "users" also has the same GID (say 1000). Then when I save
a file as deon:users on any system - if that system exports a filesystem via NFS, any other system I can still access it (because deon:users = 2000:1000).

So if you are sharing stuff to your PI - and the files are owned paulie420:users, and the Pi application is running as pi:users - while "paulie420" and "pi" can have different UIDs - your users group should have the

same GID. Then if you files and dirs have g=rwx (then your "pi:users"
user can read your files on the NAS that are owned by paulie420:users).

(Its perfectly legal that the UID for "pi" and "paulie420" be the same number, then u=rwx would apply.)

IE: It doesnt matter what the text is for a user or a group (that's for
us humans), its the IDs that they map to that is important for access control.

Now, if you doing stuff as "root", then there is a different issue to address -

since NFS can map root to "nobody" if nfs_root_squash is used (its a protective

thing, but it can trip you up every now and again).

What he said! =)
I was gonna say in a round about way almost exactly this. UID's and GID's

You could "cheat" the system a little, if the NFS mount is purely gonna be used

by you and you alone, then just chmod 777 the lot, however I would do what Deon

said. Matching UID's and GID's is the way to go.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07�� |08[|10eml|08] |15ml@erb.pw |07�� |08[|10web|08] |15www.erb.pw |07��Ŀ |07�� |08[|09fsx|08] |1521:1/158 |07�� |08[|11tqw|08] |151337:1/101 |07�� |07�� |08[|12rtn|08] |1580:774/81 |07�� |08[|14fdn|08] |152:250/5 |07��
|07�� |08[|10ark|08] |1510:104/2 |07��

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

From paulie420@1337:3/129 to deon on Wed Mar 24 17:05:51 2021

So cross device NFS is a pain...

Ok, but... I'm following a lot of what you just typed. I am familiar with like... level 1 permissions on a local box. I'm not great with (or, I just haven't had a need until NOW...) groups or userIDs. However, I've added my user

to a group before on the NAS system and understand groups a LITTLE.

So... I do know that my UID is 1001 on the NAS system. I'm reading about NFS permissions and think that I'll be able to figure things out.

I'm probably off base, but... could I create a 'pi' user with read/write access

on the NAS system, which is the NFS? This is one of the problems with tech and users who use it passively/not in a true production environment; we learn what we need to know to get the thing GOING - and don't grasp all of the ways it works with the system/other systems.

Anyway, at least I know what I need to do... and I'm hunting all those bits of information that will let me doso. Ugh. :P

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

From deon@1337:2/101 to paulie420 on Thu Mar 25 13:34:21 2021

Re: Re: NFS File Area Issue
By: paulie420 to deon on Wed Mar 24 2021 05:05 pm

Howdy,

Ok, but... I'm following a lot of what you just typed. I am familiar with

like... level 1 permissions on a local box. I'm not great with (or, I just haven't had a need until NOW...) groups or userIDs. However, I've added my user

to a group before on

the NAS system and understand groups a LITTLE.
So... I do know that my UID is 1001 on the NAS system. I'm reading about

NFS permissions and think that I'll be able to figure things out.

So imagine you are logged into your NAS - and in a directory it has a file like

this:

#ls -al

-rw-r----- 1 paulie420 users 1561 Mar 25 12:39 My_File

If "paulie420" is UID 1001 and "users" is GID 1000, then this is actually:

-rw-r----- 1 1001 1000 1561 Mar 25 12:39 My_File

Where:

* The size of "My_File" is 1561 bytes in size,
* Anybody with UID can read/write (the first rw-)
* Anybody with GID can only read (the second r--)
* Any user who is not the UID and is not in a group with the GID has no access (the third ---)

When you present this file to your PI via NFS - it is still the same:

-rw-r----- 1 1001 1000 1561 Mar 25 12:39 My_File

And the access rules still apply (as above).

So if you want to be able to read the file, you must:
* Be a member of a group that has GID 1000, OR
* Be a user with UID 1001.

You can only write to the file, if you are a user with UID 1001.

And if you are not a user with UID 1001, and not in a group with GID 1000, then

you cant access the file at all.

I'm probably off base, but... could I create a 'pi' user with read/write

access on the NAS system, which is the NFS?

No, wont make any difference. Users actually dont need to exist on the NAS - becase all access control decisions are based on "numbers" not "text" (that represents users and group names).

...��

... I think sex is better than logic, but I can't prove it.
--- SBBSecho 3.13-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

From paulie420@1337:3/129 to deon on Sat Mar 27 12:10:00 2021

So imagine you are logged into your NAS - and in a directory it has a
file like this:
Where:
* The size of "My_File" is 1561 bytes in size,
* Anybody with UID can read/write (the first rw-)
* Anybody with GID can only read (the second r--)
* Any user who is not the UID and is not in a group with the GID has no access (the third ---)

So if you want to be able to read the file, you must:
* Be a member of a group that has GID 1000, OR
* Be a user with UID 1001.

Deon, thank you much. So.. I knew permissions enough to get me around my LOCAL systems. And have been treating remote systems the same way - or at least, attempting to.

Thats where I began to fail and couldn't figure my way out. Your message really

explained all three things I needed to understand; and I can understand other text on permissions out there on the web much better now.

I've simply been doing things wrong. AGAIN, I messed up permissions - I had a really nice gopher going and now some of my directories files are not accessible - but no matter, I think you just gave me all the knowledge I need, and I can now understand even deeper texts on permissions. THANK YOU.

I am going to fix up my NAS and these gopher directories. Appreciated.

|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

Sysop:	Saxainden
Location:	Littleton, CO
Users:	30
Nodes:	10 (0 / 10)
Uptime:	15:12:36
Calls:	359
Calls today:	1
Messages:	36,383

NFS File Area Issue

Who's Online

Recent Visitors

System Info