From: Roman Mamedov <rm@romanrm.net>
To: g6094199@freenet.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: FYI: *buntu - btrfs kernel error
Date: Sat, 2 Jul 2016 03:29:30 +0500 [thread overview]
Message-ID: <20160702032930.7ccb1d26@natsu> (raw)
In-Reply-To: <dc10db83-ce23-161e-0307-9011f4ed4ec7@chefmail.de>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Fri, 1 Jul 2016 20:09:55 +0200
g6094199@freenet.de wrote:
> he guys,
>
> yes i know its *buntu xenial and nobody knows what they have backported,
> but maybe its still interesting for someone....
That's not an error, but just a warning that some operation was taking so
long, that the kernel was concerned it might be hung. You can adjust the
warning time threshold from 120 seconds back and forth as you like via the
sysfs interface.
What you're missing to report is whether or not the system works fine after
this, or the FS operations lock up entirely and server requires a reboot. If
it works fine, then you shouldn't worry about this too much.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-07-01 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 18:09 FYI: *buntu - btrfs kernel error g6094199
2016-07-01 18:24 ` Chris Murphy
2016-07-01 18:25 ` Chris Murphy
2016-07-01 18:57 ` g6094199
2016-07-01 22:29 ` Roman Mamedov [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=20160702032930.7ccb1d26@natsu \
--to=rm@romanrm.net \
--cc=g6094199@freenet.de \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).