Hello,
v2 is expected to become the default soon
That is good to hear.
But from the sound of it Qu has enough
information to maybe track down the v1 problem and fix it, and
probably should be fixed as v1 is the default and is still supported
and will be forever.
That's good to hear.
For me, the question now is, whether we should chase this Bug or not. I
encountered it three times while filling a 8TB drive with 7TB. Now, I
have 1TB left and I am not sure I can reproduce, but I can try.
I don't think it's necessary unless Qu specifically asks.
Let me know Qu.
you wouldn't want to constantly dump
that amount of information into kernel message buffer and then burden
the system logger with quite a lot of extraneous information.
I understand. Still, a a pitty.
Once you have a reproducer, then you can change the scheduler and see
if your reproduce steps still reproduce the problem.
I will try and let you know. It's not persistent.
Greetings,
Hendrik
