From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jaegeuk Kim <jaegeuk.kim@samsung.com>,
Jens Axboe <axboe@kernel.dk>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: mkfs.f2fs gets stuck with "blk_update_request: bio idx 0 >= vcnt 0" on 3.8
Date: Tue, 02 Apr 2013 10:27:25 +0400 [thread overview]
Message-ID: <1364884045.3301.18.camel@slavad-ubuntu> (raw)
In-Reply-To: <5159EC3D.2020501@gmail.com>
On Tue, 2013-04-02 at 00:21 +0400, Max Filippov wrote:
[snip]
> >
> > Could you share "cat /proc/partitions" and "strace mkfs.f2fs /dev/mmcblk0p3" outputs? I think that these outputs can be very useful for issue analysis.
> >
> > By the way, can you reproduce the issue on another SD-card? Do you reproduce the issue only under pandaboard?
>
> Yes, I can reproduce it on three SD cards of different vendors and different sizes.
> Unfortunately ATM I don't have any other board to try it on.
>
> # cat /proc/partitions
> major minor #blocks name
>
> 179 0 7782400 mmcblk0
> 179 1 40131 mmcblk0p1
> 179 2 32130 mmcblk0p2
> 179 3 5685248 mmcblk0p3
>
As I see, you have several partition on your SD-card. How did it
prepared?
> strace output is the following:
>
[snip]
> write(1, "Info: sector size = 512\n", 24) = 24
> write(1, "Info: total sectors = 11370496 ("..., 45) = 45
> write(1, "Info: zone aligned segment0 blka"..., 41) = 41
> fstat64(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(179, 3), ...}) = 0
> ioctl(3, BLKDISCARD
As I understand, the BLKDISCARD ioctl (to pre-discard all blocks on an
ssd, or a thinly-provisioned storage device) is a visible reason of the
issue. Unfortunately, as I see, mkfs.f2fs doesn't support option to
format partition without blocks discard step.
So, I think that it needs to investigate issue in the direction of
BLKDISCARD code on the kernel side. It makes sense to debug
f2fs_trim_device() method of mkfs.f2fs utility too. But I can't see
anything strange in this function at a glance.
With the best regards,
Vyacheslav Dubeyko.
>
>
next prev parent reply other threads:[~2013-04-02 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 17:19 Max Filippov
2013-04-01 19:27 ` Vyacheslav Dubeyko
2013-04-01 20:21 ` Max Filippov
2013-04-02 6:27 ` Vyacheslav Dubeyko [this message]
2013-04-02 15:41 ` Max Filippov
2013-04-04 2:00 ` Max Filippov
2013-04-05 1:53 ` Shaohua Li
2013-04-05 2:18 ` Max Filippov
2013-04-05 7:57 ` Namjae Jeon
2013-04-05 15:01 ` Max Filippov
[not found] ` <CAKYAXd_q2oUiQBoLX77Yurs1OQ5cMACCGSYFOqgjPhxhErp9hA@mail.gmail.com>
[not found] ` <CAMo8BfJd9U+HAPqh-6XThHCXMCP35oLEyMXhYhPX_ZE5utD2LQ@mail.gmail.com>
2013-04-07 2:45 ` Namjae Jeon
2013-04-07 1:58 ` Shaohua Li
2013-04-07 2:21 ` Max Filippov
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=1364884045.3301.18.camel@slavad-ubuntu \
--to=slava@dubeyko.com \
--cc=axboe@kernel.dk \
--cc=jaegeuk.kim@samsung.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®