this post was submitted on 19 Oct 2023
32 points (92.1% liked)

Linux

48655 readers
352 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

A moment ago I unmounted my 1TB HDD with 400GB of content and I partition it into two different partitions, obviously keeping the space that was already occupied. I did because I don't care if the content get corrupted, but after I did it everything is still working perfectly, when I thought everything would be corrupted.

I am possibly a complete ignorant on this subject, but due to the nature of the HDD and how it writes and reads data I expected it to corrupt everything, why didn't it happen? On an SSD on the other hand I would not consider that possible because it is not even a mechanical part where the information is stored.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago (1 children)

Awesome question.

The operating system, or OS, really does not care about whether it is a hard drive or a solid state drive when moving around the partitions.

Say your hard drives are pools. One is filled with molasses, and the other has water. The partitions are like the ropes in the pool. Perhaps you have no ropes. Maybe you have three, but two are so close to the wall, and each other, that only a small amount of stuff could occupy those lanes.

That leaves you with one really large lane. That's your data partition.

Water or molasses, the ropes are the same.

[–] xantoxis 3 points 1 year ago (2 children)

I kinda really want a description of the mental model that led to "HDD can't do this but SSD can".

[–] [email protected] 3 points 1 year ago

As I said, I am not an expert on the subject, my mentality comes from the fact that my concept of partitions was that they were overwritten, like making a scratch on a DVD and the content could not be read because of that.

[–] [email protected] 2 points 1 year ago (1 children)

I think the idea comes from "HDD slow," as he was impressed with the speed it was happening at, especially if you think of it as requiring data to be moved around on the disk. It's not really intuitive to think of it as just a table on the disk somewhere that says which regions belong to which partition, and having those regions be anywhere on the disk.

[–] [email protected] 2 points 1 year ago (1 children)

Is that actually how it works? I thought that was only within the partition itself, while partitions are physically separate on the platter.

[–] [email protected] 4 points 1 year ago

For SSD's, it's 100% a logical table, because data is stored all over the place for load balancing purposes, so it already uses a logical table to keep track of what each block is for at any given point in time.

For HDD's, historically they were physically separated, and they mostly are still, but there's still a logical table, and there's no reason the logical table can't say "Blocks 0 through 1234 and 2000 are part of partition 1" if you have something somewhere else that you want on that partition.