Hi Petr,
On 2014/12/28 0:36, Petr Janecek wrote:
Hello Satoru and all,
that Oct. report was the only time I've experienced the error, so I
don't have much to add. I can try to answer your questions:
Here are my questions.
1. Is your system "btrfs scrub" clean?
yes,
2. Is this message shown every boot time?
no, I have seen them only during one boot
3. Is this message shown only in boot?
As in my Oct. email
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/39721
I've seen a similar one after creating a subvolume on a new fs.
But it was during the same boot.
4. When this message is started to be shown?
5. Do you have any trouble, change your operation or configuration
just before the answer of Q4 ?
a disk was added to the fs and balance has been run. The balance
crashed, as in https://bugzilla.kernel.org/show_bug.cgi?id=64961
(probably unrelated). After reboot, I've seen the messages.
Additional questions.
Q5. Could you give me your kernel configuration?
At least, could you tell me whether your kernel
enabled CONFIG_PREEMPT or not?
CONFIG_PREEMPT_VOLUNTARY=y
Q6. If the answer of Q1 is correct, please give me the
file system image which can be captured by the following command.
Sorry, the fs's are long gone. I continued to run similar workloads on
that test box, but these errors never appeared again.
Thank you for giving me information.
So, further investigation of this problem seems to be hard.
Please give us the above-mentioned information if this problem
happens again.
Thanks,
Satoru
Regards,
Petr
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
