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
u
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 t
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,
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
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 do
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
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 dri
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 woul
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
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è
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
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 th
12 matches
Mail list logo