Permanent drives should be put wherever you want them to, for example I have mine mounted in /ld1 for Large Disk 1. /media is supposed to be used by systems to mount things you plug, but some systems move that to /var/run/media or other places. /mnt is there so you don't have to create a folder in case you want to mount something really quick.
this post was submitted on 04 Jul 2024
126 points (97.7% liked)
Linux
47341 readers
1156 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Thanks man.
Mount your internal disks to /D:, /E:, /F:, etc.
🥇
IMO you should use LVM2 or one of the high level filesystems that have similar features, and then dynamically create partitions and mount them as needed. E.g. Suddenly need 50G for a new VM image? Make a partition and mount it where you need the space.
If I'm not wrong LVM is a method which joins all your disk into single storage pool.
Let's say I stored data all across my LVM, now I remove one of the disks. What happen now?
You are correct, LVM combines 1 or more disks into 1 or more storage pools that can then be allocated out to logical volumes as needed.
If you just up and pull a disk from a pool (volume group), you're gonna have a bad time. You can, however, migrate the "extents" allocated to that physical disk to another in order to replace the disk, and your logical volumes can be set up with RAID-like redundancy. There's a lot of options on how to manage it.
Thank you for explaining.
No problem! To expand further, I am 99% certain it would be perfectly viable to have a single disk volume group and just take advantage of LVM's ability to create, resize and delete virtual partitions on the fly. I think you could also put all your disks into a single volume group, then ask it to not spread your logical volumes across multiple disks, if you wanted to. Could get a bit fiddly though.
That depends on your usecase.
I have setup servers where I mounted extra drives on /srv/nfs
When/If I switch to Linux I will probably mount my secondary drives to folders like
/home/stoy/videos
/home/stoy/music
/home/stoy/photos
/home/stoy/documents
/home/stoy/games
The ~/games will probably be an LVM since it contains little critical data and may absolutely need to be expanded to span several drives, though I would also be able to reduce the size of it and remove a drive from the LVM if needed.
I'd make a simple conky config to keep track of the drive space used
I'd just keep using the default automount spot for automounting drives.
If I'm not wrong LVM is a method which joins all your disk into single storage pool.
Let's say I stored data all across my LVM, now I suddenly remove one of the disks. What happen now?
Also can I add more disks to LVM later?
Yep, LVM is basically a software raid 0, I used it when setting up Linux server VMs for years at my last job, as far as I know they are still running fine.
The VM system backed up all VMs regularly, so I used LVMs as it made increasing the storage on a server easier for me.
Since it is just a raid 0 that can span several disks and one disk failiure can bring it down I don't want any irriplacable data on it, so games from Steam seems like an excellwnt idea.
That also means that being able to just have a volume spanning several disks would be an easy and simple way to increase storage when space is running tight.
I am an avid hobby photographer and I would never trust an LVM without some kind of added protection, I am looking to get a Synology NAS with minimum of four drives raided in raid 5.
I have a very old Intel NAS with used drives that I used for many years, but I don't trust it anymore, I keep it powered off as a cold backup.
Thank you.
My /home is also on a separate filesystem, so in principle I don't like to mounting data under there, because then I cannot unmount /home (e.g. for fsck purposes) unless I unmount also all the other filesystems there. I keep all my filesystems on LVM.
So I just mount to /mnt and use symlinks.
Exception: sshfs I often mount to home.
So you suggest not to mount like the guy above said /home/stoy/videos ?
And suggest symlinks instead?
Yes, just mount to /mnt/videos and symlink that as needed.
I guess there are some benefits in mounting directly to $HOME, though, such as find/fd work "as expected", and also permissions will be limited automatically per the $HOME permissions (but those can be adjusted manually).
For finding files I use plocate, though, so I wouldn't get that marginal benefit from mounting below $HOME.
Thank you.
Idk, I mount my disks in /mnt/whatever, though I don't think it matters where you mount them.
Thanks.
view more: next ›