From: "Ian! D. Allen" <idallen@idallen.ca>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume snapshot hung in btrfs_commit_transaction
Date: Sat, 11 Dec 2010 22:43:39 -0500 [thread overview]
Message-ID: <20101212034339.GA26170@idallen.ca> (raw)
This is a second try to post this follow-up, with the dmesg log info
deleted. What is the size/length limit on this mailing list?
On Thu, Dec 09, 2010 at 02:46:39PM -0500, Ian! D. Allen wrote:
> Hello developers - Last chance to get more details on this btrfs hang
> (below) before I reboot the machine. Anything I can do to gather
> more data?
Too late. The machine eventually hung and had to be rebooted. I've saved
that hung btrfs disk partition (185GB) if anyone wants to contact me to
examine it further.
I put in a larger disk (250GB), set up a partition for btrfs, and ran
the same continuous snapshotting test. It got up to creating snapshot
150 and then btrfs hung again. So the bug is repeatable and makes btrfs
0.19 on Ubuntu 10.10 unusable.
# ps laxgww | awk '$10 ~ /D/ {print }'
0 0 3723 28355 35 - 6224 332 btrfs_ DN+ pts/7 0:00 btrfs subvolume snapshot /mnt/sdb1/snap000150 /mnt/sdb1/snap000151
1 0 27334 2 20 0 0 0 wait_f D ? 0:02 [btrfs-transacti]
I ran an "ls" on the root of the btrfs partition and it hung, too,
as does anything trying to access anything in that partition:
0 777 10005 3732 20 0 21856 692 vfs_re D pts/11 0:00 ls -abp --color=auto /mnt/sdb1
Here are the blocked process WCHANs:
# ps -o wchan 3723 27334 10005
WCHAN
btrfs_commit_transaction
wait_for_commit
vfs_readdir
Here is what appeared in /var/log/kernel.log regarding the above processes:
2010-12-11T10:47:32.583745-05:00 linux kernel: [43201.070404] INFO: task btrfs-transacti:27334 blocked for more than 120 seconds.
[... 175 more related dmesg lines deleted ... ]
--
| Ian! D. Allen - idallen@idallen.ca - Ottawa, Ontario, Canada
| Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/
| College professor (Free/Libre GNU+Linux) at: http://teaching.idallen.com/
| Defend digital freedom: http://eff.org/ and have fun: http://fools.ca/
next reply other threads:[~2010-12-12 3:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 3:43 Ian! D. Allen [this message]
2010-12-12 8:14 ` btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-12 9:45 ` btrfs subvolume list fails to show all snapshots Ian! D. Allen
2010-12-13 8:47 ` Li Zefan
2011-01-20 23:01 ` Ian! D. Allen
2011-01-21 2:03 ` Li Zefan
2010-12-14 2:23 ` btrfs subvolume snapshot hung in btrfs_commit_transaction Ian! D. Allen
2010-12-17 1:47 ` Chris Mason
2010-12-17 4:45 ` Ian! D. Allen
2010-12-17 14:52 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 14:01 Ian! D. Allen
2010-12-09 19:46 ` Ian! D. Allen
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=20101212034339.GA26170@idallen.ca \
--to=idallen@idallen.ca \
--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).