-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2021-10-25 at 04:23 +0200, Carlos E. R. wrote:
On Monday, 2021-10-25 at 03:07 +0200, Carlos E. R. wrote:
On Monday, 2021-10-25 at 00:50 +0200, Carlos E. R. wrote:
On Sunday, 2021-10-24 at 21:02 +0200, Carlos E. R. wrote:
On Sunday, 2021-10-24 at 10:37 -0400, Anton Aylward wrote:
On 2021-10-24 08:18, Carlos E. R. wrote:
...
Meanwhile, I asked for a sync of the old partition (on rotating rust), and it is taking longer than writing this post.
+++............. the command was issued at 16:53 hours.
Now it is 20:43 and is still running.
It is taking hours to run. Not finished at the moment of sending this email, at 21:01
.............++-
Still running at 00:49
Still running at 03:03
I just did this:
Telcontar:~ # date --rfc-3339=seconds ; time umount -v /data/Lareiserfs 2021-10-25 03:01:46+02:00 umount: /data/Lareiserfs: target is busy.
real 0m0.004s user 0m0.002s sys 0m0.000s Telcontar:~ # lsof /data/Lareiserfs lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME sync 10237 root 3r DIR 8,41 280 2 /data/Lareiserfs Telcontar:~ # date --rfc-3339=seconds ; time umount -v --lazy Telcontar:~ /data/Lareiserfs 2021-10-25 03:02:08+02:00 umount: /data/Lareiserfs (/dev/sdc9) unmounted
real 0m0.003s user 0m0.003s sys 0m0.000s Telcontar:~ #
That way I'm sure nothing is writing to that partition.
And leave sync running the sync during the night, let's see tomorrow.
Wow, it finished!
Telcontar:~ # time strace -o /tmp/hibernate_old.strace sync -f Telcontar:~ /data/Lareiserfs/
real 674m20.295s user 0m0.005s sys 0m0.092s Telcontar:~ #
Telcontar:~ # date --rfc-3339=seconds 2021-10-25 04:15:00+02:00 Telcontar:~ #
About 12 hours!
Telcontar:~ # cat /tmp/hibernate_old.strace ... fcntl(3, F_SETFL, O_RDONLY|O_LARGEFILE) = 0 syncfs(3) = 0 close(3) = 0 close(1) = 0 close(2) = 0 exit_group(0) = ? +++ exited with 0 +++ Telcontar:~ #
I see something writing every second or so to /dev/sdc9 (in gkrellm), even though umounted. There should be nothing writing to it.
Hum, now it is gone... :-?
Will try to hibernate and call it a day.
It took an hour and a half to hibernate! Telcontar:~ # hibernate 2021-10-25 04:23:46+02:00 Checking news to send 2021-10-25 04:23:49+02:00 Syncing 2021-10-25 06:03:59+02:00 synced. Now screensaver xscreensaver-command: no screensaver is running on display :0.0 touch /var/lib/news/bin/cronscriptparafetchnews.enabled Telcontar:~ # I see write activity on /dev/sdc9, which is umounted, gkrellm is showing it. I'm going to reboot, maybe the kernel still has open inodes on it. ... Rebooted. Interesting, now I see that low intensity write activity on /dev/nvme0n1p6 instead, the new small reiserfs partition for news. See attached photo of gkrellm displaying the partition, labelled "nv 6". Each vertical line is about 14K/S write. News fetching is still disabled, but thunderbird might be reading them. Telcontar:~ # ps afxu | grep news ... news 10624 1.2 0.0 73324 9512 ? Ss 10:52 0:00 /usr/lib/systemd/systemd --user news 10625 0.0 0.0 268436 4396 ? S 10:52 0:00 \_ (sd-pam) After using thunderbird: news 10720 0.0 0.0 13492 5496 ? Ss 10:53 0:00 /usr/sbin/leafnode So Thunderbird was not still reading. The previous entry of systemd could be "leafnode.socket": Telcontar:~ # systemctl status leafnode.socket ● leafnode.socket - Leafnode NNTP server Loaded: loaded (/usr/lib/systemd/system/leafnode.socket; enabled; vendor preset: disabled) Active: active (listening) since Mon 2021-10-25 10:40:58 CEST; 14min ago Listen: [::]:119 (Stream) Accepted: 1; Connected: 1 Tasks: 0 CGroup: /leafnode.socket Oct 25 10:40:58 Telcontar systemd[1]: Listening on Leafnode NNTP server. Telcontar:~ # Ah, the write activity on /dev/nvme0n1p6 is gone, but instead I have it on /dev/sdc9! Can't be news related now: Telcontar:~ # mount | grep sdc9 /dev/sdc9 on /data/Lareiserfs type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /usr/share/flightgear type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /usr/src type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /data/homedvl type reiserfs (rw,relatime,lazytime,user_xattr,acl) /dev/sdc9 on /home/cer/terrasync type reiserfs (rw,relatime,lazytime,user_xattr,acl) Telcontar:~ # Even the bind mountpoint is renamed: Telcontar:~ # l /data/Lareiserfs total 6 drwxr-xr-x 11 root root 280 Oct 24 19:07 ./ drwxr-xr-x 26 root root 4096 Oct 24 14:12 ../ drwxr-xr-x 2 root root 160 Jan 20 2018 MoveReiser/ drwxr-xr-x 3 root root 72 Mar 2 2014 data_homedvl/ drwxr-xr-x 7 root root 240 Jan 14 2019 gamedata/ drwxrwxr-x 7 root root 168 Oct 23 15:03 pruebas/ drwxr-xr-x 2 root root 72 Feb 2 2018 scripts/ drwxr-xr-x 21 root root 1240 Oct 15 23:24 usr_src/ drwxrwxr-x 15 news news 472 Oct 23 14:16 var_spool_news.no/ Telcontar:~ # Telcontar:~ # lsof /dev/sdc9 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. Telcontar:~ # Telcontar:~ # time sync -f /data/LareiserfsOnSSD/ real 0m0.016s user 0m0.001s sys 0m0.000s Telcontar:~ # time sync -f /data/Lareiserfs/ real 0m0.092s user 0m0.001s sys 0m0.000s Telcontar:~ # Now I see the write acctitivity on both /dev/nvme0n1p6 and /dev/sdc9. I wonder what is causing that write activity on sdc9. There should be nothing. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYXZzUhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV6bwAni3MhuLgmQj2mS7DGYHK RQ5xu73uAJ4vp9dTJlTjogd/PQm1KUo+C0vuzA== =TjHs -----END PGP SIGNATURE-----