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. 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. On Sun, 14 Mar 2021 20:39:51 -0700 Marc Shapiro via Dng <dng@lists.dyne.org> 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. > > > Marc
pgpj92yggPs5Q.pgp
Description: Signature digitale OpenPGP
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
