From: Marc MERLIN <marc@merlins.org>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.15-rc5 deadlocked a 2nd time after I was copying photos from an sdcard + common code path that deadlocks all btrfs filesystems
Date: Tue, 17 Jun 2014 07:40:09 -0700 [thread overview]
Message-ID: <20140617144009.GG19071@merlins.org> (raw)
In-Reply-To: <539FE03F.5030306@jp.fujitsu.com>
On Tue, Jun 17, 2014 at 03:29:19PM +0900, Satoru Takeuchi wrote:
> Hi Marc,
>
> (2014/05/19 22:49), Marc MERLIN wrote:
> >Ok, that's 2 out of 2.
> >
> >I was copying pictures from an sdcard (through mmcblk0), and the
> >filesystem deadlocked.
> >
> >Unfortunately, when this happens, I copied my pictures (which were still
> >in RAM) to my 2nd drive which was also btrfs.
>
> From your sysrq capture, your sd card is formatted as VFAT, is it correct?
Yes, typical camera sdcard :)
> ===
> [194790.140892] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some
> data may be corrupt. Please run fsck.
> ===
>
> Did you try mkfs.fsck? In addition, does this problem happen
> after that? Here try to reproduce with 3.16-rc1 is desirable.
Tat was almost a month ago. The card has been reformatted since then, but
the problem was not with the sdcard or vfat FS. All the data was read fine,
ended up in the page cache, and btrfs failed to actually commit it to disk.
> If it's easy to reproduce,
>
> - run fsck.vfat (as I described before),
> - change SD card,
> - change copy target to other filesystem than btrfs
>
> is useful to find out the root cause.
I wish I could reproduce this at will, but I can't. In some way, that's good
since I lost actual pictures (from Japan at the time) each time this
happened.
Either way, thanks for having a look.
I'll answer the rest in another message since it warrants another thread.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-06-17 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 13:49 3.15-rc5 deadlocked a 2nd time after I was copying photos from an sdcard + common code path that deadlocks all btrfs filesystems Marc MERLIN
2014-06-17 6:29 ` Satoru Takeuchi
2014-06-17 14:40 ` Marc MERLIN [this message]
2014-06-17 14:59 ` frustrations with handling of crash reports Marc MERLIN
2014-06-17 18:27 ` Marc MERLIN
2014-06-18 13:23 ` Konstantinos Skarlatos
2014-06-18 21:22 ` Duncan
2014-06-19 8:56 ` Konstantinos Skarlatos
2014-06-19 15:06 ` Duncan
2014-06-19 15:19 ` Duncan
2014-06-19 17:37 ` Chris Murphy
2014-06-19 15:13 ` Marc MERLIN
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=20140617144009.GG19071@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.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).