From: Martin Bakiev <mbakiev@gmail.com>
To: toth.f.janos@gmail.com, llowrey@nuclearwinter.com,
linux-btrfs@vger.kernel.org
Subject: Re: Possible deadlock when writing
Date: Sat, 1 Dec 2018 16:21:13 -0700 [thread overview]
Message-ID: <ABEF1951-66FC-48F8-A7C4-0D499F48AF84@gmail.com> (raw)
I was having the same issue with kernels 4.19.2 and 4.19.4. I don’t appear to have the issue with 4.20.0-0.rc1 on Fedora Server 29.
The issue is very easy to reproduce on my setup, not sure how much of it is actually relevant, but here it is:
- 3 drive RAID5 created
- Some data moved to it
- Expanded to 7 drives
- No balancing
The issue is easily reproduced (within 30 mins) by starting multiple transfers to the volume (several TB in the form of many 30GB+ files). Multiple concurrent ‘rsync’ transfers seems to take a bit longer to trigger the issue, but multiple ‘cp’ commands will do it much quicker (again not sure if relevant).
I have not seen the issue occur with a single ‘rsync’ or ‘cp’ transfer, but I haven’t left one running alone for too long (copying the data from multiple drives, so there is a lot to be gained from parallelizing the transfers).
I’m not sure what state the FS is left in after Magic SysRq reboot after it deadlocks, but seemingly it’s fine. No problems mounting and ‘btrfs check’ passes OK. I’m sure some of the data doesn’t get flushed, but it’s no problem for my use case.
I’ve been running nonstop concurrent transfers with kernel 4.20.0-0.rc1 for 24hr nonstop and I haven’t experienced the issue.
Hope this helps.
next reply other threads:[~2018-12-01 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 23:21 Martin Bakiev [this message]
2018-12-03 9:36 ` Possible deadlock when writing Tony Lambiris
-- strict thread matches above, loose matches on Subject: below --
2018-11-26 18:18 Larkin Lowrey
2018-12-01 15:15 ` Janos Toth F.
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=ABEF1951-66FC-48F8-A7C4-0D499F48AF84@gmail.com \
--to=mbakiev@gmail.com \
--cc=CANznX5GqHJwx+y6b9kruzYXEP93oEhRtHyG_yuWwHV286+fQdw@mail.gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=llowrey@nuclearwinter.com \
--cc=toth.f.janos@gmail.com \
/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).