On Sat, 9 Jan 2021 09:49:22 -0800
John Jason Jordan <[email protected]> dijo:
>I can't figure out why I suddenly have new folders on my laptop in
>/media/jjj/disk, media/jjj/disk1, and /media/jjj/disk2. The first two
>appear to have all the folders of /, that is, bin, boot, dev, etc,
>home, lib, lib64, media, meta, mnt, opt, proc, root, run, sbin, snap,
>srv, sys, tmp, usr, var, plus writable. I've never seen a folder named
>'writable' before. The file manager says each of the first two is a
>102MB volume. Looking inside each of the folders they seem to have
>parts of what is really in /, but not all. The third folder has bin,
>etc, firstrun, lib, man1, meta, snap, tests, usr, and the files
>chromium.png, command-chromium.wrapper, and flavor-select. WTH?
>
>I have an rsync script that runs every night via cron to copy / to a
>folder 'Root' on another drive, mounted at /media/jjj/data:
>
>#!/bin/bash
>TS=`date`
>rsync -avx --delete
>--exclude-from=/home/jjj/Software/Rsync_root_excludes.txt /
>/media/jjj/Data/Root echo "$TS Root Backup Done Exit Status $?" >>
>/home/jjj/Software/Rsync_daily_log.txt
>
>Every morning when I sit down at the computer the daily log is sitting
>in the middle of the screen, displaying exit code 0, and waiting for me
>to close it. It gets there via another cron job that calls gxmessage to
>display it.
>
>When I saw these bogus folders I immediately thought that they must
>have gotten there via this script, but that doesn't make sense. First,
>the script has been running every night for a long time, but one of the
>folders was apparently created on 9/29, the second one on 10/8, and
>the third one on 12/3.
>
>I'm pretty sure I could just delete these folders with no harm
>resulting, but how did they get there in the first place? Why?
>
>I'd like to solve this mystery, but I could use some clues.
More information: In the Gnome Disk Utility all three appear, and there
is some text underneath:
102MB Loop Device
/var/lib/snapd/snaps/core_10126.snap (deleted)
102MB Loop Device
/var/lib/snapd/snaps/core_10185.snap (deleted)
254MB Loop Device
/var/lib/snapd/snaps/chromium_1421.snap (deleted)
And on the other side of the Gnome Disk Utility it says:
Device /dev/loop3 (Read-Only)
Contents Unknown (squashfs 4.0)
Device /dev/loop5 (Read-Only)
Contents Unknown (squashfs 4.0)
Device /dev/loop9 (Read-Only)
Contents Unknown (squashfs 4.0)
So it appears that the culprit is snap. I've never understood what the
advantage of snap is, but I think it is now required, at least on the
'buntus. I still don't know why it created these devices, and if it
needed them, why it didn't get rid of them.
_______________________________________________
PLUG: https://pdxlinux.org
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
