<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Ami Sapphire's Notices</provider_name>
 <provider_url>http://cwcyrix.nsupdate.info/gnu-social/public/</provider_url>
 <title>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 14-Jun-2023 13:37:43 EDT</title>
 <author_name>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)</author_name>
 <author_url>http://cwcyrix.nsupdate.info/gnu-social/public/index.php/amisapphire</author_url>
 <url>http://cwcyrix.nsupdate.info/gnu-social/public/notice/104</url>
 <html>Seems the file corruption issue no longer occurs after these reallocation events as well. I'll keep watch; will have to get a replacement HDD if it gets nearly bad enough.&lt;br /&gt;
&lt;br /&gt;
On another note, my main webserver OS drive (where this very microblogging instance is hosted) actually has 14 reallocated sectors from the original 0 over the years... and the original issue was a stuck UNC that a zero-write cleared (and the bad sector count remained at 0). That was back in October 2011, when the server was migrated to Linux.</html>
</oembed>
