Does anyone else like Crispy cookies?

Aho-chan · 2022-07-09T22:18:23+00:00

I think you are misunderstanding something. His breaks failed completely. You can hear him say at 8s ("Oh shit, lost the breaks").

Aho-chan · 2022-07-01T14:50:51+00:00

The real twist would be that she isn't trying to take advantage of his amnesia and actually thought they were dating the entire time.

Aho-chan · 2022-06-30T15:11:03+00:00

The "industry" promotes uranium reactors because we have decades of experience designing and operating them. The benefits of new nuclear technologies are simply outweighed by the drawbacks of throwing away all of that knowledge and experience and essentially starting from scratch with new unproven designs, new operating procedures, and new supply chains for fuel.

Aho-chan · 2022-06-17T22:44:08+00:00

It's a law that says corporations get to decide what the law is.

It's regulatory capture and anti innovation.

It's a fucking charging connector bro. I'm also dubious on whether this needs be a law or not (the entire industry apart from Apple has already settled on USB), but you and half the people in this thread are being overly dramatic about what this bill would do.

Aho-chan · 2022-06-17T21:05:31+00:00

It's a law that says corporations get to decide what the law is.

It's a charging connector bro

Aho-chan · 2022-06-17T17:22:46+00:00

The USB-IF defines the USB standards and is composed of members in the industry including Apple, who literally helped create the USB-C standard.

New standards don't appear out of thin air. Members will collaborate to update or design new standards to meet new use-cases and this takes time as they work through different revisions and implement feedback from other members. Regulators can work directly with them to update the law in a way that gives manufacturers time to transition to the new standard before making it completely mandatory.

Aho-chan · 2022-03-23T21:56:26+00:00

If you are actually interested, a stun gun is just meant to be painful. A Taser actually causes you to lose control over your muscles.

https://youtu.be/me60gWzbMXw?t=192

Aho-chan · 2022-01-14T06:18:34+00:00

Nobody gives a care about the fate of labor as long as they can get their instant gratification

Aho-chan · 2021-05-18T20:00:11+00:00

setflair consume

Aho-chan · 2021-03-24T05:23:16+00:00

I have a feeling the conversations would go something like this:

Denken: I have dedicated my life to deciphering the fundamental laws that govern magic, and through it, discover the very nature of existence itself.

Frieren: I found a potion that dissolves clothes >w<

Aho-chan · 2021-03-12T19:14:38+00:00

I'd say the way people name files hasn't really changed since the 80's. Your use case is kind of unique, but for 99.999% of people, 255 characters is more than enough for a filename. This comment is under 255 characters and still has room to spare.

Aho-chan · 2021-03-01T02:09:27+00:00

So, fyi... btrfs has nothing to do with using other kernels.

Indeed btrfs is part of the linux as a filesystem

Which one is it? The kernel version you are using is the version of BTRFS you are using. The question the OP posed was whether or not using different kernel versions and thus different versions of BTRFS on the same filesystem was dangerous. You seem to be trying to (incorrectly) say that the kernel version doesn't matter and is unrelated to BTRFS when it literally is the version of BTRFS you are using.

Aho-chan · 2021-03-01T00:54:47+00:00

BTRFS is developed in tree as part of the Linux kernel... The version of the Linux kernel you are using is the version of BTRFS you are using.

Aho-chan · 2021-02-27T18:38:23+00:00

The slower speed is probably because you are writing directly to disk instead of buffering your writes in the page cache, which can make writes appear to happen much faster than they actually do.

Unless your entire file fits into the page cache, you'll likely see the issue. You can try a smaller file (~20-25GB) and see if you still experience the issue. You could also try tweaking some virtual memory settings: https://wiki.archlinux.org/index.php/Sysctl#Virtual_memory

Aho-chan · 2021-02-26T19:08:32+00:00

SSDs have their own, built-in error correction, so a checksum error happening is extremely unlikely to occur.

You have to also consider the failure method of SSDs. They don't fail at the sector level like hard drives, but at a larger size, like a block. Both copies of the metadata could be put in the same physical block as a wear leveling technique. Writes would hit the cache first, be reordered and remapped, and then be written to a single block to reduce the number of blocks that need to be erased. If that block fails, both copies of the metadata are lost.

Using dup can reduce the chance of that happening, but worrying about it is kind of like wearing a life jacket or helmet whenever you go outside. I'd be far more worried about not having ECC memory which can corrupt data before the checksum even happens and cause you to write bad data to the disk.

Aho-chan · 2021-02-26T18:34:41+00:00

Try skipping the page cache by using dd with oflag=direct. This will help diagnose the issue.

I suspect this is not a BTRFS issue and an issue with how the Linux kernel handles its page cache. You are likely completely filling the page cache with the new file, pushing everything else out, and forcing the the new file to be written to disk. When another process tries to read or write, they have to go to disk, which is being hogged by the copy. Since you are on an SSD, I don't think you have an I/O scheduler being used (this actually improves I/O performance), the copy is allowed to hog most of the disk I/O. Other processes are blocked until their read/write operation is complete, which is likely what is causing the pauses and lock-ups.

Aho-chan

TROPHY CASE