linux-ext4 - Re: regression: 4.13 cannot follow symlinks on some ext3 fs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6644604d-b7b3-d836-927d-1bfecc3fa6eb@thelounge.net>
Date:   Sun, 26 Nov 2017 22:35:08 +0100
From:   Reindl Harald <h.reindl@...lounge.net>
To:     linux-ext4 <linux-ext4@...r.kernel.org>
Cc:     Dave Chinner <david@...morbit.com>
Subject: Re: regression: 4.13 cannot follow symlinks on some ext3 fs



Am 26.11.2017 um 22:14 schrieb Dave Chinner:
> On Sun, Nov 26, 2017 at 10:40:26AM -0500, Theodore Ts'o wrote:
>> Are you
>> running some benchmarks that are logging into the root, and that's
>> triggering the ENOSPC condition?
> 
> No, I'm not doing anything like that on these machines. It's
> straight forward "something filled the root fs unexpectedly" type of
> error which I don't notice immediately...

have you ever considered to just buy larger disks or introduce quota 
because "Unlike ext3, ext4 is not a filesystem that takes kindly to 
being abused by an environment that involves machines being crashed, 
oopsed and forcibly rebooted without warning tens of times a day" caused 
by a full root fs is anyhting but a reasonable workload and i doubt any 
filesystem is intended to run under such abused environment

it would be even enough to not run that workload as root because that's 
the reserved diskspace is for