Re: [DNG] rm not freeing space
On Mon, 15 Mar 2021 20:36:28 -0700 Marc Shapiro via Dng wrote: > I'm not familiar with sfill. What does it do and what package is it > in. It is not currently installed here. > > Marc sfill is part of secure-delete. rm doesn't actually remove data, it just remove all links to it leaving the space available to be used by something else. secure-delete scramble the data with junk (several times) so nothing can be recovered. pgpgIldYjm8c3.pgp Description: Signature digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On 3/15/21 2:48 AM, Bernard Rosset via Dng wrote: You are correct. I used '+L' NOT '-L'. I would add -nP -> "lsof -nP +L1" If negative, I would go for the ugly path, grep'ing lsof's output on "deleted" or "(deleted)". Past this point, if space of alleged deleted files is not cleared... I wonder. Even ext2 should do the trick. If not ext4, I would upgrade to it by changing the flags with the help of tune2fs. I am especially surprises by the fact that you stated you could unmount the volume and remount it, still without seeing free space improvement... Are you positive you deleted the real files, and not mere links to them? I would make sure by using du to seek for actual disk usage location. In a last, desperate resort, I would try to force allocation/release of free space through sfill I'm not familiar with sfill. What does it do and what package is it in. It is not currently installed here. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On 3/15/21 8:23 PM, Arnt Karlsen wrote: On Mon, 15 Mar 2021 19:54:20 -0700, Marc wrote in message <74553f6b-2616-70e1-e742-1ce9275b3...@gmail.com>: On 3/15/21 6:31 AM, Hendrik Boom wrote: On Sun, Mar 14, 2021 at 10:28:32PM -0700, Marc Shapiro via Dng wrote: On 3/14/21 10:09 PM, Ludovic Bellière wrote: I assume you read the man page of fsck, as it's return code is what you want to pay attention to. As for lsof, the correct parameters would be `lsof +aL1 /dev/sdx. It should have thrown an error were you to use `lsof -L1`. If lsof returns nothing, your drive is most likely corrupted. You are correct. I used '+L' NOT '-L'. It may also be possible that the files you removed have other references on your file system, aka. hard links. To find them, you would need to know the inode number, either by using `stat` or `ls -i`. You can then find them using `find -inum`. Since you already removed the files, you most likely can't know the inode number. However you could throw a `find $path -size n[cwbkMG]` to list the files with the matching size. I'm not following you on this. What is this going to do for me? 'find' is only going to show undeleted files. How does this help? It is possible for a single file to be hard-linked in several places in the file system. If so, removing it in one place will still leave it accessible from another, and therefore not deleted. Files have reference counts to keep track of this. These files should not have any links, hard or soft. None of the other files in that directory show a reference count above 1. They are backup files created by fsarchiver. I'm just trying to free up space by deleting files from January. ..any chance they have white-space-character-only names? E.g. " ", " ", " " etc, or Norwegian æ, ø, å, or some invisible non-Latin alphabet soup not supported by your fonts nor locales? You should still be able to cut-n-paste those and have them show up as high-lighted boxes. No. These are file that had names when I deleted them. I wrote/modified the scripts that generated the filenames, so all of the characters came from my keyboard. I hate names with spaces in them, so there weren't any spaces or hidden characters in them. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On Mon, 15 Mar 2021 19:54:20 -0700, Marc wrote in message <74553f6b-2616-70e1-e742-1ce9275b3...@gmail.com>: > On 3/15/21 6:31 AM, Hendrik Boom wrote: > > On Sun, Mar 14, 2021 at 10:28:32PM -0700, Marc Shapiro via Dng > > wrote: > >> On 3/14/21 10:09 PM, Ludovic Bellière wrote: > >>> I assume you read the man page of fsck, as it's return code is > >>> what you want to pay attention to. > >>> > >>> As for lsof, the correct parameters would be `lsof +aL1 /dev/sdx. > >>> It should have thrown an error were you to use `lsof -L1`. If > >>> lsof returns nothing, your drive is most likely corrupted. > >> You are correct. I used '+L' NOT '-L'. > >>> It may also be possible that the files you removed have other > >>> references on your file system, aka. hard links. To find them, you > >>> would need to know the inode number, either by using `stat` or > >>> `ls -i`. You can then find them using `find -inum`. > >>> > >>> Since you already removed the files, you most likely can't know > >>> the inode number. However you could throw a `find $path -size > >>> n[cwbkMG]` to list the files with the matching size. > >> I'm not following you on this. What is this going to do for me? > >> 'find' is only going to show undeleted files. How does this > >> help? > > It is possible for a single file to be hard-linked in several > > places in the file system. If so, removing it in one place will > > still leave it accessible from another, and therefore not deleted. > > > > Files have reference counts to keep track of this. > > These files should not have any links, hard or soft. None of the > other files in that directory show a reference count above 1. They > are backup files created by fsarchiver. I'm just trying to free up > space by deleting files from January. ..any chance they have white-space-character-only names? E.g. " ", " ", " " etc, or Norwegian æ, ø, å, or some invisible non-Latin alphabet soup not supported by your fonts nor locales? You should still be able to cut-n-paste those and have them show up as high-lighted boxes. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On 3/15/21 6:31 AM, Hendrik Boom wrote: On Sun, Mar 14, 2021 at 10:28:32PM -0700, Marc Shapiro via Dng wrote: On 3/14/21 10:09 PM, Ludovic Bellière wrote: I assume you read the man page of fsck, as it's return code is what you want to pay attention to. As for lsof, the correct parameters would be `lsof +aL1 /dev/sdx. It should have thrown an error were you to use `lsof -L1`. If lsof returns nothing, your drive is most likely corrupted. You are correct. I used '+L' NOT '-L'. It may also be possible that the files you removed have other references on your file system, aka. hard links. To find them, you would need to know the inode number, either by using `stat` or `ls -i`. You can then find them using `find -inum`. Since you already removed the files, you most likely can't know the inode number. However you could throw a `find $path -size n[cwbkMG]` to list the files with the matching size. I'm not following you on this. What is this going to do for me? 'find' is only going to show undeleted files. How does this help? It is possible for a single file to be hard-linked in several places in the file system. If so, removing it in one place will still leave it accessible from another, and therefore not deleted. Files have reference counts to keep track of this. These files should not have any links, hard or soft. None of the other files in that directory show a reference count above 1. They are backup files created by fsarchiver. I'm just trying to free up space by deleting files from January. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On 3/15/21 12:55 AM, Steve Litt wrote: Wait!!! Make sure you run only a non-destructive fsck. If the non-destructive fsck shows no problem, do the following... First run the sync command. The sync command forces all caches to be written to their respective files. If they're on a removeable drive, my next step after sync would be to unmount the drive. Then physically disconnect it. Then physically reconnect it. Then remount it. Then do your df -h. Already did this. See my original post. Also, if your removeable drive is some sort of SSD, you might need to do fstrim, although I swear I remember space deleted but not yet trimmed doesn't count in df. But I could be wrong. Removable spinning disk. SteveT Ludovic Bellière said on Mon, 15 Mar 2021 04:33:37 +0100 Run fsck to make sure your disk isn't corrupted or damaged. Afterward, your lost+found might get populated with the stuff that occupies the space, done so in order for you to review. On Sun, 14 Mar 2021 20:10:03 -0700 Marc Shapiro via Dng wrote: I had some large files (over 200GB in total size) that I no longer needed. So I removed them. They no longer show up in the directory. However, df, still shows the space as being used. I understand that if processes are still using the files they will not be removed until the processes either release them, or are shut down (or killed). I have tried using 'lsof -a -L1 MOUNTPOINT' to list the open, but deleted files. It returns no files at all. These files are on a removable drive. I can unmount the partition and disconnect the drive, then reconnect the drive and remount the partition, but the space still shows as being used. If the files are still open, shouldn't 'umount' give an error? I would rather not have to shut down the system. Is there some other way to determine what is keeping these files open, or otherwise preventing the space from being reclaimed? Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Shutting down on weird keys combination.
On Friday 12 March 2021 at 19:51:41, А. Сорокин via Dng wrote: > Hello. > > I have a strange behavior on my system (DeVuan's Sid (Ceres?) > up-to-date system): on quick pressing (may be it seems to system as keys > are pressed at once), of Shift-b-v (no matter where: CLI or GUI) system > shuts down normally. I have a few questions / suggestions: 1. Do you mean you press Shift, release it, press b, release it and press v, all in quite quick succession, or do you mean Shift+b (so, a capital B), release both, and then press v? It would be good to know what you are trying to type at the time this occurs. 2. Does the same thing occur if you plug in an external keyboard and type the same things on that? 3. What does syslog say as the machine shuts down (tail the file in one window while you type in another, or else SSH from somewhere else to watch the file as you type the magic combination)? 4. Does it also happen in Beowulf (try a Live CD if you don't still have that installed as dual-boot)? Antony. -- "In fact I wanted to be John Cleese and it took me some time to realise that the job was already taken." - Douglas Adams Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Shutting down on weird keys combination.
Hello. On Sat, 13 Mar 2021 13:27:16 +1100, you wrote: > You’re not accidentally pressing the SysRq key at the same time? Of course not! Only Shift-b-v . Now i think it is not a bad thing, but i never saw this before, and do not know if i'n alone with this. If alone, then i have a virus probably, if not, rhen i would like to know what does that. Andrey. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
You are correct. I used '+L' NOT '-L'. I would add -nP -> "lsof -nP +L1" If negative, I would go for the ugly path, grep'ing lsof's output on "deleted" or "(deleted)". Past this point, if space of alleged deleted files is not cleared... I wonder. Even ext2 should do the trick. If not ext4, I would upgrade to it by changing the flags with the help of tune2fs. I am especially surprises by the fact that you stated you could unmount the volume and remount it, still without seeing free space improvement... Are you positive you deleted the real files, and not mere links to them? I would make sure by using du to seek for actual disk usage location. In a last, desperate resort, I would try to force allocation/release of free space through sfill Bernard (Beer) Rosset https://rosset.net/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
On Sun, 14 Mar 2021 20:39:51 -0700 Marc Shapiro via Dng wrote: > > On 3/14/21 8:33 PM, Ludovic Bellière wrote: > > Run fsck to make sure your disk isn't corrupted or damaged. > > Afterward, your lost+found might get populated with the stuff that > > occupies the space, done so in order for you to review. > > Already looked in lost+found. Nothing there. > > Tried fsck. It says the partition is clean. Did you "force" the fsck (with '-f'), or did you rely on the filesystem's "marked as clean" flag? libre Grüße, Florian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space
Wait!!! Make sure you run only a non-destructive fsck. If the non-destructive fsck shows no problem, do the following... First run the sync command. The sync command forces all caches to be written to their respective files. If they're on a removeable drive, my next step after sync would be to unmount the drive. Then physically disconnect it. Then physically reconnect it. Then remount it. Then do your df -h. Also, if your removeable drive is some sort of SSD, you might need to do fstrim, although I swear I remember space deleted but not yet trimmed doesn't count in df. But I could be wrong. SteveT Ludovic Bellière said on Mon, 15 Mar 2021 04:33:37 +0100 >Run fsck to make sure your disk isn't corrupted or damaged. Afterward, >your lost+found might get populated with the stuff that occupies the >space, done so in order for you to review. > >On Sun, 14 Mar 2021 20:10:03 -0700 >Marc Shapiro via Dng wrote: > >> I had some large files (over 200GB in total size) that I no longer >> needed. So I removed them. They no longer show up in the >> directory. However, df, still shows the space as being used. I >> understand that if processes are still using the files they will not >> be removed until the processes either release them, or are shut down >> (or killed). I have tried using 'lsof -a -L1 MOUNTPOINT' to list the >> open, but deleted files. It returns no files at all. >> >> These files are on a removable drive. I can unmount the partition >> and disconnect the drive, then reconnect the drive and remount the >> partition, but the space still shows as being used. If the files are >> still open, shouldn't 'umount' give an error? >> >> I would rather not have to shut down the system. Is there some >> other way to determine what is keeping these files open, or >> otherwise preventing the space from being reclaimed? >> >> Marc >> >> ___ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
