Linux NILFS development
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Anthony Doggett
	<Anthony2486-fDpYTK8McCxDP812hmKXO1pr/1R2p/CL@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mkfs.nilfs2 -b 1024 -B 8192
Date: Wed, 10 Apr 2013 10:19:14 +0400	[thread overview]
Message-ID: <1365574754.2577.5.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130409210827.GA3809-P/DK4avwC2n/PtFMR13I2A@public.gmane.org>

Hi Anthony,

On Tue, 2013-04-09 at 22:08 +0100, Anthony Doggett wrote:
> Hi Vyacheslav
> 
> I've been curious as to what within the "darcs whatsnew" was causing the
> "nilfs_direct_assign: invalid pointer: 0" / "broken bmap" issue for 1kB
> blocks and I had a quiet half hour today, so I've boiled it down to a
> simpler script and a short bit of C.  I include both below just in case
> you should find them useful.  I was surprised to see that the 'a' makes
> it to the file despite the filesystem errors.
> 

Thank you.

I am using your previous script for the issue investigation. I have a
picture of the issue but I don't find the reason of it yet. I think that
I'll use your new script during investigation.

Thanks,
Vyacheslav Dubeyko.

> Kind regards,
> Anthony

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-04-10  6:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  7:14 mkfs.nilfs2 -b 1024 -B 8192 Anthony Doggett
     [not found] ` <20130313071453.GA17072-P/DK4avwC2n/PtFMR13I2A@public.gmane.org>
2013-03-13  8:25   ` Vyacheslav Dubeyko
2013-03-13 14:27     ` Anthony Doggett
     [not found]       ` <20130313142726.GA3328-9gBkq9fxGAp+urZeOPWqwQ@public.gmane.org>
2013-03-14  6:40         ` Vyacheslav Dubeyko
2013-03-14 18:14   ` Vyacheslav Dubeyko
     [not found]     ` <424816AD-A79B-4F3D-A886-8D0CC735812B-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-04-09 21:08       ` Anthony Doggett
     [not found]         ` <20130409210827.GA3809-P/DK4avwC2n/PtFMR13I2A@public.gmane.org>
2013-04-10  6:19           ` Vyacheslav Dubeyko [this message]

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=1365574754.2577.5.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=Anthony2486-fDpYTK8McCxDP812hmKXO1pr/1R2p/CL@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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