On Sun, 14 Mar 2021 22:28:32 -0700
Marc Shapiro via Dng wrote:
> > 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
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,
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
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
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
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
