From: Adrian Hunter <adrian.hunter@nokia.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: Ronny Dierckx <ronny.dierckx@telenet.be>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Bityutskiy Artem \(Nokia-M/Helsinki\)"
<Artem.Bityutskiy@nokia.com>
Subject: Re: UBIFS synchronisation questions about file create/delete
Date: Fri, 27 Nov 2009 15:44:57 +0200 [thread overview]
Message-ID: <4B0FD7D9.5060904@nokia.com> (raw)
In-Reply-To: <000001ca6f65$4752a8e0$d5f7faa0$@dierckx@telenet.be>
Ronny Dierckx wrote:
>> No it is not normal behaviour.
>>
>> 10 minutes is long enough for everything to be written and flushed. The
> file
>> should be completely intact.
>>
>> No UBIFS operations which change directory entries are not entirely
>> synchronous. There is a NAND-page-sized buffer which must be flushed.
>> It is flushed every 5 seconds or so. Otherwise you must do some kind of
>> sync.
>>
>> I can only guess that that version of UBIFS is somehow broken.
>
> Hi Adrian,
>
> I tried some different versions from
> git://git.infradead.org/~dedekind/ubifs-v2.6.27.git
> and the problem is caused by commit " UBIFS: fix 64-bit divisions in debug
> print "
> 9d016dc4b3006ef3493b21442394028614e26da5 :
>
> dbg_io("set timer for jhead %d, %llu millisecs", wbuf->jhead,
> - ktime_to_ns(wbuf->hardlimit)/USEC_PER_SEC);
> - hrtimer_start(&wbuf->timer, wbuf->hardlimit, HRTIMER_MODE_REL);
> + div_u64(ktime_to_ns(wbuf->hardlimit), USEC_PER_SEC));
> }
>
> As you can see the timer is no longer started. Could you please fix this ?
It is Artem's git tree.
Artem, can you look at this?
next prev parent reply other threads:[~2009-11-27 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 21:06 UBIFS synchronisation questions about file create/delete Ronny Dierckx
2009-11-27 8:19 ` Adrian Hunter
2009-11-27 8:53 ` Jamie Lokier
2009-11-27 13:26 ` Ronny Dierckx
2009-11-27 13:44 ` Adrian Hunter [this message]
2009-11-27 14:21 ` Artem Bityutskiy
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=4B0FD7D9.5060904@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ronny.dierckx@telenet.be \
/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