On Thu, Feb 18, 2021 at 08:46:02PM +0000, Samir Benmendil wrote: > On Feb 17, 2021 at 16:56, Samir Benmendil wrote: > > On 17 February 2021 13:45:02 GMT+00:00, Hugo Mills <h...@carfax.org.uk> > > wrote: > > > On Wed, Feb 17, 2021 at 01:26:40PM +0000, Samir Benmendil wrote: > > > > Any advice on what to do next would be appreciated. > > > > > > The first thing to do is run memtest for a while (I'd usually > > > recomment at least overnight) to identify your broken RAM module and > > > replace it. Don't try using the machine normally until you've done > > > that. > > > > Memtest just finished it's first pass with no errors, but printed a note > > regarding vulnerability to high freq row hammer bit flips. > > > > I'll keep it running for a while longer. > > 2nd pass flagged a few errors, removed one of the RAM module, tested again > and it passed. I then booted and ran `btrfs check --readonly` with no > errors. > > [root@hactar ~]# btrfs check --readonly /dev/mapper/home_ramsi > Opening filesystem to check... > Checking filesystem on /dev/mapper/home_ramsi > UUID: 1e0fea36-a9c9-4634-ba82-1afc3fe711ea > [1/7] checking root items > [2/7] checking extents > [3/7] checking free space cache > [4/7] checking fs roots > [5/7] checking only csums items (without verifying data) > [6/7] checking root refs > [7/7] checking quota groups skipped (not enabled on this FS) > found 602514441102 bytes used, no error found > total csum bytes: 513203560 > total tree bytes: 63535939584 > total fs tree bytes: 58347077632 > total extent tree bytes: 4500455424 > btree space waste bytes: 15290027113 > file data blocks allocated: 25262661455872 > referenced 4022677716992 > > > Thanks again for your help Hugo.
Great news. Hugo. -- Hugo Mills | The early bird gets the worm, but the second mouse hugo@... carfax.org.uk | gets the cheese. http://carfax.org.uk/ | PGP: E2AB1DE4 |
Description: PGP signature