Beiträge von LostCatchphrases

    Oh yes!


    As far as I'm aware aufs respects pooled file permissions as a design decision. I did have a look around the man page but nothing was too forthcoming. I suspect we'll need to create a fairly robust script to chown and chmod things down a pooled directory. I can generate sort of a basic pseudocode for what needs to be done but that's about where my expertise stops. I'll look at learning bash scripting once I've gotten all of my assessments under control.

    Quote from LostCatchphrases: “Changing permissions on a pooled share with Aufs doesn't seem to change the actual permissions on the disk the file is actually stored.”


    That's been discussed several times in permission issues related threads. The most…


    I did a few searches earlier and only found people's problems with Aufs seemed to be that it didn't always balance. They did mention that Aufs might be the culprit in passing but I figured if people were trying to make a decision on Mhddfs or Aufs they should probably know what issues they might run into while using it. At least if they're using it the way I did.


    I'll do another more thorough search on permissions issues now but I do like your idea. I'd have to do a lot more research into what Aufs does behind the scenes before I'm comfortable mucking about with it, but I'll keep playing with a smaller subsystem once I've gotten my housemates watching TV reliably. I'm still coming to terms with the command line, I've been coddled too much by Windows it seems!

    Hey guys, just wanted to relay some experiences and notes I've learned about Aufs whilst troubleshooting my system here.


    Currently my home setup consists of 11 drives (with space for 13) of varying degrees of space and reliability. I set up SnapRaid and a few media sharing systems and decided on Aufs as my drive pooling solution.


    All was well and good, but I noticed after a while that some folders I dumped into drone factory were failing, or a comics folder dumped into a general share wasn't accessible. I deleted the folder, but alas it was still there somehow! That, coupled with weird permissions problems prompted me to dig deeper. I enlisted the help of a friend, together we granted a user account ownership of a test file and chmodded it to 777, got onto Putty and then flicked over to it. We could see the file, we could write another file in the same directory but alas renames or anything just weren't working.


    It turns out Aufs just says that it's changed the permissions, on the drives themselves the permissions remain the same. At least in my case, I've also noticed that deletes are a bit hit and miss and moves were a bit... more miss than hit really. Of course this makes it a pain in the metaphorical when I'm using a combination of SAB, Couch and Sonarr to throw files around my drives like poo in the monkey pit. I also want to make it clear that this doesn't mean Aufs is broken. The logic behind making Aufs respect underlying file permissions is simply so that data you don't want shared out with the wrong users isn't inadvertently exposed when a drive is pooled. It just means that in my context it's not super useful, especially since I'm a noob and still trying to work out the best sets of permissions/see how things interact.


    I mostly deduced all this from spending far too much quality time with WinSCP, and also looking up articles like this one: http://zackreed.me/articles/84…with-mhddfs?view=comments


    The one thing I'll miss is Aufs' speed which I've seen saturate gigabit connections. I hear Mhddfs is slower but only time will tell before I can know for sure.


    Summing it all up:
    - Changing permissions on a pooled share with Aufs doesn't seem to change the actual permissions on the disk the file is actually stored.
    - My deletes didn't always delete
    - My moves very often didn't move
    - Speed was godly


    If I weren't still trying to learn how to Linux and my data was a bit less mobile I would definitely keep using Aufs, but for now I'm going to try the other option Ryecoaaron kindly added.

    Okay I think I found the cause of my issues, I was checking through the other tabs on WebGUI and found the support info one.


    This is up the top of the file, I'm reasonably certain it's not meant to be there as it's not commented out. <sharedfolder>


    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
    <name>xxx</name>
    <comment>xxx</comment>
    <mntentref>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</mntentref>
    <reldirpath>xxx</reldirpath>
    <privileges>
    <privilege>
    <type>user|group</type>
    <name>xxx</name>
    <perms>0 = no permission|5 = read and execute|7 = read, write and execute</perms>
    </privilege>
    </privileges>
    </sharedfolder>
    <sharedfolder>
    <uuid>ba102545-d1bc-4aab-ae3f-406a51f80cb7</uuid>
    <name>Movies</name>
    <comment></comment>
    <mntentref>06c34ff7-7aa3-417f-877e-54ea7cbabb75</mntentref>
    <reldirpath>Shares/Movies/</reldirpath>
    <privileges>
    <privilege>
    <type>user</type>
    <name>plex</name>
    <perms>7</perms>
    </privilege>
    </privileges>
    </sharedfolder>
    <sharedfolder>
    <uuid>852a36d8-0cd1-403e-a480-2f81f9e88655</uuid>
    <name>TV</name>


    [Edit]
    Forum removed all the tabs present in the support info, but that first block is almost centred with the amounts of tabs stuffed in it.
    [Double edit]
    Dangit, I found the direct config.xml file and it appears that it's a template for what they're supposed to look like... Also appears commented out in the config.xml file itself. I am noticing that the mntref (assuming "mount reference"?) is not the mountpoint for Rusthaven itself, which is /media/4c02c547-ade4-44d2-bb26-5ea6fff6e836


    ------------------------
    Additional update!
    ------------------------


    I got desperate and installed OMV on a spare drive I had, and it appears sharing works! I'm still not sure if this is a Linux permissions issue or a config issue but I still have the old disks if someone wants to pick it apart. For now I'm just regularly backing up the config.xml file and I'm going to experiment as necessary. tekkb appears to have made a guide specifically for sharing PLEX on OMV so I'll start on that first and then move to less problematic things.

    Hi everyone,


    I appear to be in a spot of bother after installing PLEX and attempting to fix it. All my Samba shares are now un-navigable and it's somewhat frustrating!


    Please keep in mind that whilst I've played with Linux in the past, this is my first actual foray into using the operating system... getting into the commandline has been tricky but fun! I can follow instructions quite well at least. I'm not putting up my configs just yet because there's a lot of them and I don't want to create a wall of text if I can help it.


    The trouble starts...
    We have PLEX running on a Windows machine and I decided after things were running smoothly that it was time to move PLEX over to our shiny new OMV setup. I was trying to fix an issue with the PLEX service flat-out refusing to start following a reboot. Right now that's secondary to getting my Samba shares back as my household uses it to host files for our Windows-based PLEX and also as a way of transferring video edits and other large files. Additionally we intend on storing backed up Steam games there for a lan party this weekend (fingers crossed) so that's my deadline. One of the suggested fixes called for manually creating a user called "plex" and another suggested I alter permissions on my media share. Since then I've found that the Samba shares are browsable but I cannot open them.


    Setup:
    We're running our shares out of a Aufs created drive called "Rusthaven" which so far comprises of 4 other drives. We have more available but they aren't in use yet. I'm not actually done configuring the server, but it was at a point where I was happy transferring stuff over from the drives failing in my old QNAP because failing drives are quite sub-optimal. In that I have Couch, lost+found, plexmediaserver (for the database), some custom folders for SAB and then Shares and Test. Shares is the main folder containing our share files. Inside there I have Games, Movies, Documents etc all shared out individually so that we can map them to drives easily. Test is naturally a test folder.


    As for installed plugins I'll give you a quick list. PLEX, as mentioned appears to be the cause of our issues.


    Samba is installed, as is Snapraid which seems to be doing a good job of existing so far. There are other plugins installed and activated, though they don't seem to be related in that they have their own folders on the root drive created by Aufs and it's not shared in any way, shape or form. The list includes SABnzbd, Couch Potato and Sonarr. I also have SSL activated so I can putty in. Very handy.


    Testing...
    Currently I've done the following:

    • Created a new share folder via Web GUI the same way I did with the initial shares. In the Shared Folders menu I give everyone read/write permission and then when creating the Samba share I ensure that it has guest only access. I leave everything else as default.
    • Manually edited smb.conf, tried changing security to share and then when that didn't work I added a line for "map to guest = bad user' after changing security back to default user.
    • Manually changing permissions using WinSCP of the test share folder to 777 to see if that lets me in, as well as changing the owner from plex to root.


    Any assistance on this matter would be greatly appreciated, cheers!
    [ninja edit for readability]