Re: Causes, cures and prevention of orphaned inodes?
- Date: Mon, 5 Feb 2018 13:06:22 -0500
- From: Cindy-Sue Causey <butterflybytes@xxxxxxxxx>
- Subject: Re: Causes, cures and prevention of orphaned inodes?
On 2/4/18, Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> wrote:
> On Sun, 04 Feb 2018, Stephen P. Molnar wrote:
>> I am running Debian Stretch on am eight thread AMD GPU platform.
>> Lately, it seems if I have been plagued by surfeit of orphaned nodes.
> That means:
> 1. "unlinked" files or directories were still open when the filesystem
> had to be shutdown/made read-only. Uncommon, unless you did something
> like breaking the system by having /run on something other than
> tmpfs, etc.
As soon as I grasped the context, similar was my kneejerk thought. I
see that inode message related to either power failure or my having to
hardcore shut the power off rather than shut down a safer, more
logical way that protects data. So my thinking is that it could be
about something [buggy] not shutting down properly or simply just in
time even if a "proper" reboot/shutdown is being performed..
For some reason, I'm tying it most often to browsers in my case, but I
can't remember why I always think that. Maybe it's most often about
browsers seeming to cause the situation or something.... ? :)
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *