Actions
(8.51 MB, 480x360 h264)
I watched this G1 MLP abridged episode/video today (~85 MB): > /z9/youtube/Scootertrix_Studios_UCB0qq3SOsKZGwM4prKK1xmA/Expert_Trackers-Scootertrix_Studios-20240208-youtube-1920x1440-BsuF-oS3zR0.webm The original video source is probably VHS, which is 240p or 360p. Here's a 360p version of that video, for an "authentic feel". Like what that one anon said about the medium or form of some media being related to or a big part of nostalgia. >>/10262/ > nerdy shit Getting into that: https://zfsonlinux.org/manpages/0.8.1/man8/zdb.8.html https://openzfs.github.io/openzfs-docs/man/master/8/zdb.8.html > The precise output of most invocations is not documented, a knowledge of ZFS internals is assumed. > zdb is an "offline" tool; it accesses the block devices underneath the pools directly from userspace and does not care if the pool is imported or datasets are mounted (or even if the system understands ZFS at all). https://wiki.lustre.org/Examining_ZFS_Pools_with_zdb > If the pool has not been imported to the current host, or if there is no zpool cache file on the host for a currently imported pool, use the following command: \ zdb -e \ This will provide a very large amount of output. To get the MOS configuration, use the following: \ zdb -eC[C] https://piped.adminforge.de/watch?v=y7gQwypNMdk https://youtubetranscript.com/?v=y7gQwypNMdk > the ZFS filesystem has a transaction log and it's continually writing to the transaction log ... the more messed up stuff is it just sort of keeps writing. When something weird happens, when an inconsistency happens, I wish that there was an option to tell ZFS: when any inconsistency is encountered that is unrecoverable to put the filesystem into read-only mode. I see why that's not an option [or default option necessarily because ZFS is designed for] racks and racks and racks of disks and you would never ... you would never necessarily want to take the entire pool offline just because there's one uncorrectable inconsistency. But for small installations where small is say less than 10 hard drives it would be nice if it would go into read-only mode because I think that greatly increases the chances that you'll be able to recover. If only. Next thing he said was: > I think that in those situations when you encounter hardware that has died that way it is more likely to be a bug at least if working with zdb is really any indication because of space maps and some of the other problems that we encountered I think we're really just down to bugs or very slight inconsistencies in the pool most of the time online when somebody encounters a situation like this they'll say oh it's probably just a little corruption in your pool make another pool and then copy all the stuff out of that pool the corrupt pool into the new pool and everything will be fine everybody does that and it seems to be not really a big deal