12/7/2023 0 Comments Archive mounter lubuntu![]() on the HDD)įor users alice and bob and adjust the permissions so that only Mount UUID=291bd44c-vvvv-xxxx-yyyy-zzzzzzzzzzzz /mnt/archiveĬreate user specific folders below /mnt/archive (i.e. Mount the archive partition into an empty directory, say /mnt/archive: mkdir /mnt/archive We assume sda is an SSD and sdb is an HDD. In my case, I have / and /home on sda and an unmounted Sdb8 ext4 archive 291bd44c-vvvv-xxxx-yyyy-zzzzzzzzzzzz Sda6 ext4 home a87c2c2d-vvvv-xxxx-yyyy-zzzzzzzzzzzz /home Sda5 ext4 slash 467ddc36-vvvv-xxxx-yyyy-zzzzzzzzzzzz / The home directories themselves areĪll commands must be issued as user root.ĭetermine UUID of archive partition: lsblk -fs The following steps describe how to mount the partition on your HDDīelow /mnt/archive and then add bind mounts to the home directories Is there a way to set up what I'm describing, or can someone please point out where my thinking about the user filesystem structure is off-base? ![]() quotas not necessary but possible storage for space on the HDDīasically, separate and secure individual user shares on the bulk storage device - extending the user's home directory - without pushing all of /home to that second device./home// on the SSD linked to / visible/accessible only to as ~/.user files and directories on HDD accessible only to that user, and linked under the user's /home.Allow setup of multi-user system, with \home on the SSD and individual user access to large-file storage on the HDD.Unfortunately, all of this a hair beyond my understanding of Linux filesytems and it is very possible that I'm just not understanding this all correctly. So far, all the two+ drive solutions I've seen just mount the HDD as bulk storage symlinked under /home, sets up /home as an LVM pseudo-RAID across the two (opinions vary whether that is a good idea, and lvmetad prevents it for now anyway), or sets up an actual RAID (which I don't want to get into). Ideally, what I want is to create a subspace of ~/home on the HDD and have it usable and understandable to someone that has no interest in filesystem management and needs it to "just work" so that she can get to her data. I'm not sure I want to just mount the HDD (e.g., as /archive) with links to /home, though, since I want whatever is pushed off to the HDD to also be exclusively part of her user space (i.e., not just generic storage accessible/visible to any other user account). I'm trying to figure out how to set up so that /home stays on the ssd (for speed, etc), with the bulk of the archival on the HDD. pdf's, and other data files) that would obviously overwhelm the SSD. She has almost 500gb of archaeological research data (many confidential/proprietary photos. ![]() Tried installing with LVM enabled, but ran into the lvmetad issue and had to go with standard ext4 partitions (i.e., just /efi and / on the SSD, single unmounted ext4 partition on the HDD that has the archive of her user data). One last thing to figure out and set up is how to handle the two drives (480GBb SSD, 1TB HDD). It's an Ubuntu-only machine (no dual boot, only one OS distro, may need to set up a VM for certain Windows-specific applications). I just switched my wife's home computer to Ubuntu 18.04 from Windows 10, and she's liking the transition so far.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |