All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Petr Janecek <janecek@ucw.cz>
Cc: <russell@coker.com.au>, <linux-btrfs@vger.kernel.org>,
	Timofey Titovets <nefelim4ag@gmail.com>
Subject: Re: Debian/Jessie 3.16.7-ckt2-1 kernel error
Date: Mon, 5 Jan 2015 10:02:29 +0900	[thread overview]
Message-ID: <54A9E2A5.50909@jp.fujitsu.com> (raw)
In-Reply-To: <20141227153621.GB19957@atrey.karlin.mff.cuni.cz>

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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      reply	other threads:[~2015-01-05  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  1:02 Debian/Jessie 3.16.7-ckt2-1 kernel error Russell Coker
2014-12-24  9:47 ` Satoru Takeuchi
2014-12-25  0:41   ` Satoru Takeuchi
2014-12-27 15:36     ` Petr Janecek
2015-01-05  1:02       ` Satoru Takeuchi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54A9E2A5.50909@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=janecek@ucw.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nefelim4ag@gmail.com \
    --cc=russell@coker.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.