linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Alexander Gordeev <alex@gordick.net>
Cc: Chao Yu <chao@kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: video archive on a microSD card
Date: Wed, 31 Aug 2016 16:46:33 -0700	[thread overview]
Message-ID: <20160831234633.GA17031@jaegeuk> (raw)
In-Reply-To: <592891472633520@web8m.yandex.ru>

On Wed, Aug 31, 2016 at 11:52:00AM +0300, Alexander Gordeev wrote:
> Hi Jaegeuk,
> 
> 29.08.2016, 21:00, "Jaegeuk Kim" <jaegeuk@kernel.org>:
> > On Mon, Aug 29, 2016 at 07:50:24PM +0300, Alexander Gordeev wrote:
> >>  Hi,
> >>
> >>  I have an update about the first of the bugs, that I reported.
> >>
> >>  19.08.2016, 20:23, "Alexander Gordeev" <alex@gordick.net>:
> >>  > Hi,
> >>  >
> >>  > I'd also like to report two bugs. I used f2fs-stable branch linux-3.10.y.
> >>  > I'm using some proprietary modules also, but in my understanding they shouldn't affect the fs.
> >>  >
> >>  > 1. I have a Sandisk 16GB microSDHC card, that is quite old and may be at its end of life.
> >>  > The bug is produced every time I try to delete any file on it.
> >>  >
> >
> > ...
> >
> >>  As you can see, after to warnings goes an oops. I think it was overlooked.
> >>  But it makes the most trouble to me.
> >>
> >>  I tried to understand what's going on.
> >>  It turns out that se->cur_valid_map is NULL in update_sit_entry().
> >>  Probably, this is not expected.
> >
> > Thank you for the analysis. :)
> > It seems the blkaddr is out-of-range.
> > Can you print out its blkaddr?
> >
> > If possible, could you print out:
> >   curseg->segno, curseg->next_blkoff,a curseg->next_segno
> >   at the end of allocate_segment_by_default()?
> 
> Thank you for the help!
> Here are the new traces:

Thank you.

> 
> [   49.274678] ------------[ cut here ]------------
> [   49.280216] WARNING: at /home/alex/work/s2l/amb_S2l_SDK_2.5/SDK2.5/s2l_linux_sdk/ambarella/kernel/linux-3.10/fs/f2fs/segment.c:1105 new_curseg+0x268/0x394 [f2fs]()

This means there is no free segment.
Could you print out the below information before this f2fs_bug_on?
- prefree_segments(sbi)
- free_segments(sbi)

> ...
> [   49.518054] ---[ end trace 49dca462b4f988ff ]---
> [   49.522689] ------------[ cut here ]------------
> [   49.527375] WARNING: at /home/alex/work/s2l/amb_S2l_SDK_2.5/SDK2.5/s2l_linux_sdk/ambarella/kernel/linux-3.10/fs/f2fs/segment.c:1144 new_curseg+0x2f0/0x394 [f2fs]()

This is caused by the above segno which was -1.

> ...
> [   49.764853] ---[ end trace 49dca462b4f98900 ]---
> [   49.857344] ------ segno = 7540, next_blkoff = 0, next_segno = 4294967295 --------
> [   49.913664] ------ blkaddr = 3889152 --------
> [   49.918173] Unable to handle kernel NULL pointer dereference at virtual address 00000000

Also, we can see next_segno was -1, which incur no se entry for this segment.
At this moment, I'd really like to see its /sys/kernel/debug/f2fs/status whether
there is really not enough free segments.

Thanks,

> ...
> 
> -- 
>  Alexander

------------------------------------------------------------------------------

  reply	other threads:[~2016-08-31 23:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 11:52 video archive on a microSD card Alexander Gordeev
2016-08-15 10:47 ` Alexander Gordeev
2016-08-15 11:41   ` Chao Yu
2016-08-15 12:22     ` Alexander Gordeev
2016-08-16 15:29       ` Chao Yu
2016-08-17  9:47       ` Alexander Gordeev
2016-08-17 15:54         ` Chao Yu
2016-08-18 11:04           ` Alexander Gordeev
2016-08-19  2:41             ` Jaegeuk Kim
2016-08-19 11:56               ` Alexander Gordeev
2016-08-22 20:52                 ` Alexander Gordeev
2016-08-23 21:12                   ` Jaegeuk Kim
2016-08-25 20:14                     ` Alexander Gordeev
2016-08-27  1:20                       ` Jaegeuk Kim
     [not found]                         ` <549571472473386@web20g.yandex.ru>
2016-08-29 18:23                           ` Jaegeuk Kim
     [not found]                             ` <9581472749471@web24h.yandex.ru>
2016-09-01 20:07                               ` Jaegeuk Kim
2016-09-02 12:15                                 ` Alexander Gordeev
2016-08-23 20:27                 ` Jaegeuk Kim
2016-08-19 17:22               ` Alexander Gordeev
2016-08-23 21:27                 ` Jaegeuk Kim
2016-08-25 20:22                   ` Alexander Gordeev
2016-08-26 16:04                   ` Alexander Gordeev
2016-08-27  1:15                     ` Jaegeuk Kim
2016-08-27 13:00                       ` Alexander Gordeev
2016-08-29 16:50                 ` Alexander Gordeev
2016-08-29 18:00                   ` Jaegeuk Kim
2016-08-31  8:52                     ` Alexander Gordeev
2016-08-31 23:46                       ` Jaegeuk Kim [this message]
2016-09-01 17:40                         ` Alexander Gordeev
2016-09-01 18:25                           ` Jaegeuk Kim
2016-09-01 19:37                             ` Alexander Gordeev
2016-09-01 20:15                               ` Jaegeuk Kim
2016-09-02 12:05                                 ` Alexander Gordeev
2016-09-02 18:50                                   ` Jaegeuk Kim
2016-08-15 12:57   ` [PATCH] f2fs: fix build for v3.10 Alexander Gordeev

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=20160831234633.GA17031@jaegeuk \
    --to=jaegeuk@kernel.org \
    --cc=alex@gordick.net \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).