All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: logfs unmount bug
Date: Wed, 31 Aug 2011 09:49:02 +0200	[thread overview]
Message-ID: <20110831074902.GA26382@logfs.org> (raw)
In-Reply-To: <CAMjNe_d2pOC9+2nSy2PA=2aigF95vZv3_A-jPyWyTXteW3mqFw@mail.gmail.com>

On Wed, 31 August 2011 12:52:54 +0530, srimugunthan dhandapani wrote:
> On Wed, Aug 31, 2011 at 11:28 AM, Jörn Engel <joern@logfs.org> wrote:
> 
> > I can do.  Can you ensure you have my patch applied, rerun the rest
> > case and send me the kernel results?
> 
> I applied your patch1  and the bonnie output is the same(stuck at
> "Creating  files in sequential order ..."). The kernel is from your
> git directory(http://git.kernel.org/?p=linux/kernel/git/joern/logfs.git;a=summary)
> I am pretty sure i applied the patch. The git diff output is below[1]
> 
>  The kernel log is at
>  https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US

600M.  And starting at line 34285 or about 0% in, the output mutates
to something like the below.  Not very useful. :(

Aug 31 12:28:06 mll kernel: [  991.561293] logfs_write_obj_alia 8,, 83,(3f(320(#2 #s #es sesaseiaslialilialilialialialialialialialialialialialialialilialialialilialialialililialialialilialialialilililialialialialialilialialiallialilialialialiaali_alj_abjo_ws_fsgfogflo lo] l4] 7581586156.561.591.9 9  [  >[7>[<7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:07 mll kernel: last message repeated 4 times
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <

Can you set LOGFS_DEBUG to 0, both to cut down the noise and in the
hope that the log output doesn't get corrupted like this again?

> While i still have your attention, i would like to point out at max
> writepage size restriction in logfs. Currently logfs has a max
> writepage size as 4K. Currently, large page nand flashes and MLC nand
> come in  8K page sizes. As the usecase for logfs is large nand
> flashes(mostly with parallel and DMA write capabilities),  it may be
> essential to remove the 4K write page size restriction.
> I was only able to change the logfs-tools for >4K writepage size. If
> you send a patch, that makes logfs useable for writepagesize >4K, i
> can try on real hardware, instead of nandsim and give you the results
> :-)

That sure sounds useful.  I'll have a look...

Jörn

-- 
"Security vulnerabilities are here to stay."
-- Scott Culp, Manager of the Microsoft Security Response Center, 2001

WARNING: multiple messages have this Message-ID (diff)
From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: logfs unmount bug
Date: Wed, 31 Aug 2011 09:49:02 +0200	[thread overview]
Message-ID: <20110831074902.GA26382@logfs.org> (raw)
In-Reply-To: <CAMjNe_d2pOC9+2nSy2PA=2aigF95vZv3_A-jPyWyTXteW3mqFw@mail.gmail.com>

On Wed, 31 August 2011 12:52:54 +0530, srimugunthan dhandapani wrote:
> On Wed, Aug 31, 2011 at 11:28 AM, Jörn Engel <joern@logfs.org> wrote:
> 
> > I can do.  Can you ensure you have my patch applied, rerun the rest
> > case and send me the kernel results?
> 
> I applied your patch1  and the bonnie output is the same(stuck at
> "Creating  files in sequential order ..."). The kernel is from your
> git directory(http://git.kernel.org/?p=linux/kernel/git/joern/logfs.git;a=summary)
> I am pretty sure i applied the patch. The git diff output is below[1]
> 
>  The kernel log is at
>  https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US

600M.  And starting at line 34285 or about 0% in, the output mutates
to something like the below.  Not very useful. :(

Aug 31 12:28:06 mll kernel: [  991.561293] logfs_write_obj_alia 8,, 83,(3f(320(#2 #s #es sesaseiaslialilialilialialialialialialialialialialialialialilialialialilialialialililialialialilialialialilililialialialialialilialialiallialilialialialiaali_alj_abjo_ws_fsgfogflo lo] l4] 7581586156.561.591.9 9  [  >[7>[<7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:07 mll kernel: last message repeated 4 times
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <7
Aug 31 12:28:06 mll kernel: <

Can you set LOGFS_DEBUG to 0, both to cut down the noise and in the
hope that the log output doesn't get corrupted like this again?

> While i still have your attention, i would like to point out at max
> writepage size restriction in logfs. Currently logfs has a max
> writepage size as 4K. Currently, large page nand flashes and MLC nand
> come in  8K page sizes. As the usecase for logfs is large nand
> flashes(mostly with parallel and DMA write capabilities),  it may be
> essential to remove the 4K write page size restriction.
> I was only able to change the logfs-tools for >4K writepage size. If
> you send a patch, that makes logfs useable for writepagesize >4K, i
> can try on real hardware, instead of nandsim and give you the results
> :-)

That sure sounds useful.  I'll have a look...

Jörn

-- 
"Security vulnerabilities are here to stay."
-- Scott Culp, Manager of the Microsoft Security Response Center, 2001
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-08-31  7:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 19:35 logfs unmount bug srimugunthan dhandapani
2011-08-05 16:03 ` Jörn Engel
2011-08-05 16:03   ` Jörn Engel
2011-08-06 14:09   ` srimugunthan dhandapani
2011-08-06 14:09     ` srimugunthan dhandapani
2011-08-08  8:31     ` Jörn Engel
2011-08-08  8:31       ` Jörn Engel
2011-08-08 14:44       ` srimugunthan dhandapani
2011-08-08 14:44         ` srimugunthan dhandapani
2011-08-09 14:58         ` Jörn Engel
2011-08-09 14:58           ` Jörn Engel
2011-08-10 11:06           ` srimugunthan dhandapani
2011-08-10 11:06             ` srimugunthan dhandapani
2011-08-12  9:34             ` Jörn Engel
2011-08-12  9:34               ` Jörn Engel
2011-08-12 17:26               ` srimugunthan dhandapani
2011-08-12 17:26                 ` srimugunthan dhandapani
2011-08-16 17:17                 ` Jörn Engel
2011-08-16 17:17                   ` Jörn Engel
2011-08-21 21:19                   ` srimugunthan dhandapani
2011-08-21 21:19                     ` srimugunthan dhandapani
2011-08-26 19:49                     ` Jörn Engel
2011-08-26 19:49                       ` Jörn Engel
2011-08-29 10:07                       ` srimugunthan dhandapani
2011-08-29 10:07                         ` srimugunthan dhandapani
2011-08-31  5:58                         ` Jörn Engel
2011-08-31  5:58                           ` Jörn Engel
2011-08-31  7:22                           ` srimugunthan dhandapani
2011-08-31  7:22                             ` srimugunthan dhandapani
2011-08-31  7:49                             ` Jörn Engel [this message]
2011-08-31  7:49                               ` Jörn Engel
2011-08-31 12:49                               ` srimugunthan dhandapani
2011-08-31 12:49                                 ` srimugunthan dhandapani
2011-08-31 14:17                                 ` Jörn Engel
2011-08-31 14:17                                   ` Jörn Engel
2011-09-01  6:08                                   ` srimugunthan dhandapani
2011-09-01  6:08                                     ` srimugunthan dhandapani
2011-09-01  9:46                                     ` srimugunthan dhandapani
2011-09-01  9:46                                       ` srimugunthan dhandapani
2011-09-01 21:34                                     ` Jörn Engel
2011-09-01 21:34                                       ` Jörn Engel

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=20110831074902.GA26382@logfs.org \
    --to=joern@logfs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=srimugunthan.dhandapani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.