From: "Szőts Ákos" <szotsaki@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Instant reboot while defragging on 3.13-rc5
Date: Sun, 29 Dec 2013 10:48:25 +0100 [thread overview]
Message-ID: <73072351.X5HJy46hkl@linux-suse.hu> (raw)
Dear list members,
I upgraded to 3.13-rc5 kernel and started to defrag my whole file system with
the following commands:
cd /
for i in */*; do if [[ "$i" != windows* ]]; then echo "------$i------"; btrfs
fi defrag -clzo -r "$i"; fi; done 2>&1 | tee /root/defrag
After 10 or 15 seconds my computer reboots itself without any warning. In
dmesg I see only the following:
[ 531.866566] btrfs: device fsid 2cc2b266-3f04-4f1c-8477-cf7efd6ac139 devid 1
transid 396679 /dev/sda7
[ 532.001919] watchdog watchdog0: watchdog did not stop!
[ 532.002719] watchdog watchdog0: watchdog did not stop!
Together with this I'm constantly getting sysfs WARNINGS into dmesg, but I
don't think this would be related:
WARNING: CPU: 5 PID: 1644 at /home/abuild/rpmbuild/BUILD/kernel-
desktop-3.13.rc5/linux-3.13-rc5/fs/sysfs/group.c:214 device_del+0x3b/0x1b0()
sysfs group ffffffff81c7e040 not found for kobject 'hidraw2'
Versions:
OS: openSUSE 13.1
Kernel: 3.13.0-rc5-1.g7127d5f-desktop
btrfs: v3.12+20131125
Ákos
reply other threads:[~2013-12-29 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=73072351.X5HJy46hkl@linux-suse.hu \
--to=szotsaki@gmail.com \
--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).