robryk @robryk@qoto.org
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).
Joined Nov 2020
@lauren I don't remember doing so. It might've been the case that ~all my conversation partners were actually good typists :P
I used ytalk a lot in my early teens and actually preferred that: you could e.g. stop typing something early, because the other person obviously already understood it. Also, typing cadence gave me much more of an impression of there being another person I'm interacting with (similar to what one gets from voice chat).
And yet this is (mostly) a store-and-forward system, so it (a) technically degrades gracefully in case of high latency (b) doesn't provide UI affordances that degrade heavily under high latencies (e.g. a typing indicator would be one). (I think that store-and-forward and, in general, latency-tolerant systems are better for multiple reasons: ability to provide some privacy guarantees, and that making them so forces the design to be simple in some ways I care about.)
On a related note, it seems to me that realtime (i.e. characters appear to all parties as one's typing them) chat systems have gone basically extinct. I wonder why; is that a consequence of domination of mobile devices, or something else?
@grrrr_shark They do have a concept of substituting with something (very) similar, and do use it for "we ran out of these tomatoes, so we'll give you the other kind (and adjust the cost accordingly)".
But the other way round. Condensing it releases heat (and increases temperature), and evaporating it absorbs heat (and decreases temperature).
@delroth It might truly be terribly inaccurate. However, there might have been no reallocation: we only know that there was an error when reading that ECC could not correct. It's possible (and likely) that the sector was physically OK and was still writeable (i.e. after writing you'd read the same thing back). In that case we just keep using the same sector (I don't know how the detection of that works exactly; I'd imagine that writing to a known-uncorrectable sector would involve an immediate readback, but does the drive know that? we surely can't read back everything).
@delroth I see ~no reason to count this against that drive in light of Reallocated_Event_Count that was equal to 0 (so, IIUC no sectors were found not to be usable anymore yet).
@delroth s/never issued/redirected all reads to one sector :P/
I think this sector would work if you wrote to it. Sadly, you end up reading from it first (probably due to some readahead/caching/other bullshit) -- see `failed command: READ FPDMA QUEUED`.
I remember having a similar problem with a PATA drive >10yrs ago, which I fixed by rebuilding a kernel that just never issued reads to HDD. I expect that there's some way to make block IO layer actually issue only a write with some flags to open (O_DIRECT?).
@grrrr_shark But I'm now really curious what caused them to be unable to deliver, given that it's not the lack of time of a car/driver (IIUC all of them have refrigerated section) and presumably not lack of chickens.
@delroth Huh. That's really surprising (the read error was not immediate, so it's not _totally_ borked, but then why it seems totally borked for writes? is that the read-errored sector that you're trying to write to?). Would you mind pasting `smartctl -a /dev/sdh` and the presentation of this error in dmesg for my curiosity?
@grrrr_shark
Did they cancel delivery of the chicken only, or the delivery in general?
@delroth Take a look at Reallocated_Sector_Ct (and Offline_Uncorrectable and Current_Pending_Sector) counters. If there are few remaining spare sectors, then the disk is really close to failure. This is indicated by Reallocated_Sector_Ct being marked as dangerously high.
Other than that, sectors that cannot be corrected with the error correction code happen at some rate. This rate can be increased by various issues that make the drive arguably broken, but it's nonzero even with totally operational drive.
@delroth No, it won't.
The sector won't be reallocated until it's written to. The reasoning behind that is that maybe the next read will actually succeed, and we should never trash that possibility without explicit instructions to do so.
@LukaszOlejnik Can you give examples of changes, outside of abuse prevention? Most of what I can come up with would have already been brought to attention by e.g. Hong Kong. The remainder of what I can think of are various reinforcements of importance of availability.
@delroth Or even s/failed/is unreadable due to crc mismatch/
@delroth Isn't this "just" a sector that failed and wasn't reallocated yet, because it wasn't written to?
@justusthane Do you know what was (roughly) the exposure duration?
There's also "that sequence of defeats over multiple ~wars was a doozy".
@SwiftOnSecurity As much as I love USCSB videos, this time they claim something that sounds nonsensical (that a gas's condensing will cause the temperature to fall further than if the substance was absent in the first place), so I'd dearly want to see an accident report in written form.
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).
Joined Nov 2020
