> On 10. Mar 2022, at 12:09, Marc Lobelle <marc.lobe...@uclouvain.be> wrote: > > Hi Toomas, > > Indeed I have problems with the local storage. This notebook has a single ssd > drive (rpool) and scrubbing it finds unrecoverable errors > > ml@mosquito:/export/home/ml# zpool status -v > pool: rpool > state: DEGRADED > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: scrub in progress since Wed Mar 9 18:41:08 2022 > 141G scanned at 179M/s, 31,0G issued at 39,2M/s, 142G total > 0 repaired, 21,91% done, 0 days 00:48:07 to go > config: > > NAME STATE READ WRITE CKSUM > rpool DEGRADED 2 0 3 > c6t0d0s0 DEGRADED 2 0 6 too many errors > > errors: Permanent errors have been detected in the following files: > > rpool/ROOT/openindiana-2022:02:16:<0x881c0> > rpool/dump:<0x1> > rpool/swap:<0x1> > /export/home/ml/.local/share/Trash/files/Capture du 2022-03-03 > 15-11-12.png > rpool/export/home/ml:<0x147d> > rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.summary.C > rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.dependency.C > rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/dbus/api/group__DBusMessageInternals.html > rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/inherit_graph_24.png > rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/modules.html > Loosing a few blocks on a 1 TB ssd is acceptable if the OS can avoid using > these faulty blocks in the future. What does zpool do if I do a zpool clear: > the faults will disappear from the status but will the faulty blocs be > avoided henceforth ? > > The corrupted files are lost but, if I do "pkg refresh --full; pkg update > -v", I assume they will be replaced. > > However if the faulty blocks are not removed from the list of usable blocks, > the faults will happen again and the drive must be considered as lost and to > be replaced
This is basically 'replace ssd and restore from backup’ case, I’m afraid. rgds, toomas > > On 3/9/22 09:22, Toomas Soome via openindiana-discuss wrote: >>> On 9. Mar 2022, at 10:15, Marc Lobelle<marc.lobe...@uclouvain.be> wrote: >>> >>> Hello, >>> >>> I got a surprising error when trying to install packages (any package, even >>> xeyes) on one of my computers running openindiana: *Error encountered while >>> retrieving data from: [Errno 5] I/O error.* >>> >>> Anybody knows what to do ? >>> >>> Thanks and best regards >>> >>> Marc >> there are two possible causes, either it is some sort of network issue >> (truss -f pkg…. and see what will get EIO), or it is issue with local >> storage (zpool scrub?). >> >> rgds, >> toomas >> >> >> _______________________________________________ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
