On Friday, April 19, 2019 at 3:12:06 PM UTC, Brad Fitzpatrick wrote: > > This is pretty surprising that a full disk could cause this. We write to > an adjacent temporary file and only once it's fully written do we rename it > into place. > > But an EIO on read as shown above is also weird. What was that about? You > "fixed" it? > > I ran SpinRite, an old disk utility, in a read only mode, and it found a bad sector. I'm guessing that SpinRite trying to read that sector a whole lot of times provoked the SSD controller to swap out the bad block for a spare. When I booted back into Linux, the EIO was gone.
> I thought we had a flag to let reindexing proceed without failing on > missing files, but maybe not? > That could be useful. -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
