/mydrive
Linux
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
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.
I think tooling only cares for partitions. So /home and / are usually runtime-critical (can be on different disks or network storage), while internal data disks count as removable, since you can unmount their partitions.
/mnt is for anything and everything. /media doesn't even exist on Arch based distros and maybe others.
/mnt
is not for everything, it is a temporary mount point. For fixed drives that are constantly mounted you should use another location (that could be anywhere in the filesystem tree).
My Files, which are inside the partition mounted in /mnt/something has root as Owner. So When I try to move something to Trash, it's not allowing me to do, Only perma delete. When saw properties it said owner is root.
Is it because mounted at /mnt?
Files under /media seems fine. and says it's owner is 'me'
IDK if I'm doing anything wrong.
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.
I used to mount network attached storage in /mnt until I had problems accessing it from a Snap. In searching for a solution it was pointed out that snaps are correct in being sandboxed from these types of folders, and users like myself are making things difficult for ourselves by using those system folders.
They said the best practice would be to mount them in a folder in your home directory. I've switched to doing that and it works great.
Mount them where you need. Not /mnt
and not /media
. Maybe /var
or its subdirectory, or /srv
, or /opt
depending on what kind of data you want to store on that partition.