Live data from Hacker News

Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

github.com

61–70 of 78 posts

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#61
post #51

Pointless and harmful to flash storage. SSD sector numbers are virtual anyway. Its like defragging emails in your inbox.

check my other comments with numbers, while small for a human being, I could see the variations benchmarking copper-rs.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#62
post #7

This is the most useless thing I've seen on here lately. It's not necessary on hard drives, as the page cache did a decent job of improving disk access even in the 90s, let alone with today's fast HDDs. And if you're on an SSD... it'll just burn that out faster. I love it!

yeah, this will definitely shorten the lifetime of an nvme.

but check my other comments, it makes a difference, even on a slow nvme. Probably the overhead of the wasted small extent, and maybe prefetching?

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#64
post #45

[flagged]

Yeah, can't wait for Linux to add the forced system update that restarts the computer while I'm away, closing all my open programs. Like the cleaning lady who ignored my DO NOT RESTART note on the PS1 at the after school daycare and nuked all my progress.

She didn't restart it, she turned it off. You underestimated their critical thinking skills.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#65
post #54

Earlier quoted context omitted.

SSDs often interface with their storage in different (larger) granularities than the OS meaning that even though the data is effectively more random at large scale due to wear leveling there are still benefits to keeping blocks that are sequential in your file sequential in the filesystem also. As well as a potential read boost, the larger blocks introduce a read-before-write issue that can allow multiple close updat…

I'm pretty sure you don't understand how threads in discussion works. But, hey. Atleast you can write ~1000 chars with absolutelly no substance fo prove that you know nothing about the topic. What a life to live.

You pretty being sure of that and not understanding the relevance of the reply, makes me very sure that you are the one without a clue. And you sound like a bit of dick on top. I wish you luck in your future endeavours.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#66
post #37

Earlier quoted context omitted.

I feel so seen right now. My partner complains about me closing apps on my phone consistently. I also have to hold myself back from defragging and continually cleaning up my storage drives. I too am nearly certain that the positive benefits are approaching nil, but I still feel it should be helpful.

[flagged]

I know it’s a late reply, but the answer is absolutely both of us are exceptionally neurotic. But in completely different ways.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#67
post #20
post #7

This is the most useless thing I've seen on here lately. It's not necessary on hard drives, as the page cache did a decent job of improving disk access even in the 90s, let alone with today's fast HDDs. And if you're on an SSD... it'll just burn that out faster. I love it!

Page caches are nice, but you would see meaningful reduction in load times for the OS and applications by getting data in order on spinning disks. Especially games that used most of your ram and loaded reasonably large level files. fat seemed particularly prone to spreading files into very small chunks across the disk surface; it's not so big of a deal when fragmented files are made up of large contiguous chunks.

When I started Linux in the 90s, I remember looking for defrag utilities and finding none, but reading that defragging wasn't really necessary under ext2, because the page cache smoothed things out and/or the fs was to some degree self-maintaining. The same with NTFS. DOS file systems needed regular defragging, of course, because they were kind of garbo anyway. But coming across a real filesystem blew my mind at the time.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#68
post #27

Earlier quoted context omitted.

iOS has never worked the way you are describing. It's easy to disprove your claim that the app is killed by just switching between different apps you have open. iOS keeps the apps open to make it fast to switch back to them.

This is literally always how iOS has worked. You can refer to the application lifecycle documentation: https://developer.apple.com/documentation/uikit/managing-you...

The page you linked to doesn't say that anywhere.

Re: Show HN: I missed the moving blocks, so I built a real Linux disk defragmenter

#69
post #37

Earlier quoted context omitted.

[flagged]

I know it’s a late reply, but the answer is absolutely both of us are exceptionally neurotic. But in completely different ways.

Never too late! =]
Post reply on HN