@Fredtx said in SAMIT: Should You Still Be Using Disk Partitions:

In a Windows world, it seems it would be better to create a Storage Space, because it gives you the flexibility to extend the storage instead of having to add/mount another virtual drive if you were to run out of space.

Exactly. Same logic applies universally, always best to have that flexibility on your platform. It has no real overhead, but protects against the unknown.

As an update to this, the issue is not resolved, but I purged a couple old nextcloud user accounts, that once deleted, and got enough space to get the needed users fully sync'd again.

I'll be spinning up a new Nextcloud instance and simply manually migrating users to it I think.

That's extremely helpful, first time hearing about this tool.

Thanks for sharing

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@JaredBusch said in Linux partitioning:

@marcinozga said in Linux partitioning:

Last option on that screen. Why? Because if your root partition fills up, your system won't boot. Having /var on separate partition reduces that risk. Think of a bad app creating gigabytes of log entries, or writing junk to database.

Better solution, don't use bad apps

You never know if an app or kernel update doesn't go nuts. Here's an example of bad kernel module causing writing gigs of logs in minutes: https://unix.stackexchange.com/questions/195360/my-var-log-is-mysteriously-filling-up-gbs-in-minutes-any-cure-before-i-re-ins

Sure it's possible, but how many times do we see this sort of thing in normal use day to day? This is the first one I've heard of in years.

Used to happen more often because bad programming was more common.

Take Ubuntu for example, it will fill up /boot after a few kernel upgrades, so anything is possible.

That's a known badly implemented system. IE bad programming. Don't use it.

Also, it has nothing to do with /var filling up.

It's just an example of partition filling up, doesn't matter which one. It proves the point that it does happen.

In your example, they are causing a new problem because they've implemented your solution to the problem.

No, it would've had the same outcome if /boot wasn't on separate partition, but under root. Eventually it would've filled up entire disk with old kernel versions. The main point is to prevent root partition from filling up, not any other mount point.

That's not really true. That's making a lot of assumptions. In reality...

It would not likely ever fill up. The scales are so different. This is where creating a separate /boot actually CREATES the risk. The very pattern you are trying to follow is the one causing the issue.

It has lots and lots of chances for humans AND monitoring systems to catch and resolve it long before becoming an issue. This should have years, typically, to be flagged rather than filling up in a day or two.

@fateknollogee said in Fedora 28 Server - Linux 101 - How do you partition your drives:

@scottalanmiller said in Fedora 28 Server - Linux 101 - How do you partition your drives:

@fateknollogee said in Fedora 28 Server - Linux 101 - How do you partition your drives:

You could do something similar to this & use /data for storing vm's

0_1529273038336_screenshot_17.png

Could do that, but it loses usable space, and is unnecessarily complex. Unless he's doing something complex with the /data partition, like using a different file system or needs to snap it separately from the OS, this is just a waste.

Also, don't use swap partitions. That's not horrible, but it's unnecessarly complex and rigid and not considered best practice today.

Swap is part of the auto-partition setup.
I did not create the swap...yes I know it says "manual" at the top

Yes, but once doing any intentional management of the storage beyond just taking the defaults, best to remove it.

@black3dynamite said in Fedora 26 auto partition:

@JaredBusch said in Fedora 26 auto partition:

@black3dynamite said in Fedora 26 auto partition:

@FATeknollogee said in Fedora 26 auto partition:

0_1497934140943_auto.PNG

For a 500gb disk, is there any reason to not accept this setup?
Should /home be on a separate VG?

What if we add another 1TB disk, that should be on a separate VG?

If you do keep the default partition and want to use KVM, you will have to store the virtual disks in /home. Or during install, you remove /home and give the rest back to /.

Why? On my desktop I keep my vdisk on a separate drive mounted as /kvm_store.

It makes sense to resize or choose a larger partition when you don't have another drive available.

The whole point of LVM is to make everything easy to change latter should you need to.

@FATeknollogee The other thing to remember is that choosing the RHVH at installation likely changes the default layouts from what we normally see in a generic minimal install.

@scottalanmiller said in Fedora Block Device Full How - Extend Partition:

@travisdh1 said in Fedora Block Device Full How - Extend Partition:

@scottalanmiller said in Fedora Block Device Full How - Extend Partition:

I'm late to the party. But the root is HUGE for Linux. We normally use 12GB. 20GB is the largest I would use. Why are you extending that? What's the goal in having the root be so large?

Whoever first set it up (it wasn't @DustinB3403), just dropped everything onto the root partition. Against every best practice ever written/known for Unix/Linux.

Still, that doesn't create a need for expanding the root in most cases.

If I would have known this before helping to fix a broken system... hindsight sadly.

Just make a new partition, don't worry about extending the existing one.

@scottalanmiller said:

@Dashrender you have to have Dynamic Disks to do this in Windows using MS tools.

Sure, but you don't when using third party tools. Again, I haven't done it in 4+ years, so I don't know what Acronis can currently do.