From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] nilfs2: fix data loss in mmap page write for hole blocks
Date: Mon, 28 Mar 2011 10:15:50 +0200 [thread overview]
Message-ID: <201103281015.50533.dexen.devries@gmail.com> (raw)
In-Reply-To: <1301240873-12035-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Hi,
On Sunday 27 of March 2011 17:47:53 Ryusuke wrote:
> From the result of a function test of mmap, mmap write to shared pages
> turned out to be broken for hole blocks. It doesn't write out filled
> blocks and the data will be lost after umount. This is due to a bug
> that the target file is not queued for log writer when filling hole
> blocks. (...)
recently I've experienced a few times data loss & hang of several applications
with ktorrent running. It seems the transfered files were mostly empty after
reboot. Related to this regression & fix?
Regards,
--
dexen deVries
[[[↓][→]]]
``In other news, STFU and hack.''
mahmud, in response to Erann Gat's ``How I lost my faith in Lisp''
http://news.ycombinator.com/item?id=2308816
--
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
next prev parent reply other threads:[~2011-03-28 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 15:47 [PATCH] nilfs2: fix data loss in mmap page write for hole blocks Ryusuke Konishi
[not found] ` <1301240873-12035-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2011-03-28 8:15 ` dexen deVries [this message]
[not found] ` <201103281015.50533.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-28 15:30 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2011-04-02 2:47 Ryusuke Konishi
2011-04-11 19:04 ` Greg KH
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=201103281015.50533.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@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 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.