public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: JiSheng Zhang <jszhang3@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS power cut issues
Date: Fri, 11 Sep 2009 17:23:14 +0800	[thread overview]
Message-ID: <2df346410909110223p87aefd2ibfe8fb11e040f56f@mail.gmail.com> (raw)
In-Reply-To: <4AA77E2A.40604@gmail.com>

Hi Artem,

2009/9/9 Artem Bityutskiy <dedekind1@gmail.com>:
> On 09/09/2009 12:45 PM, JiSheng Zhang wrote:
>>>
>>> On Wed, 2009-09-02 at 17:35 +0800, JiSheng Zhang wrote:
>>>>
>>>> If we cut power when copy file into ubifs, then remount ubifs and try
>>>> to read the file, we found that the data at some offset of the file
>>>> began different from the data of the original file at the same offset.
>>>> Is this a bug of ubifs?
>>>
>>> This is expected behavior on any asynchronous FS. You may switch to
>>> synchronous behavior with '-o sync' mount option. I wrote a lot of
>>
>> I have tested with "mount -o sync", the result is the same. It's not
>> empty file. For example:
>> cp fileA /mnt/ubifs/fileB
>> random cut power before "cp" completed.
>> then remount
>>  From head of /mnt/ubifs/fileB to some offset offsetC is the same as
>> fileA. But from offsetC to the end is different from fileA at the same
>> offset offsetC, it's not empty either.
>> Hope I expressed myself clearly.
>
> Hmm, ok. What is your kernel version?
>
> Could you please take a closer look and see if these differences
> are zeroes or not?

My mistake, sorry. I have look from the offset to the end of the file,
they're really 0, that is file hole.
>
> Do you have an automated test for this? Can you share your script?

Hmm, I just run copy manually and diff once mounted again.
>
> --
> Best Regards,
> Artem Bityutskiy (Артём Битюцкий)
>

Best Regards,
Jisheng

  reply	other threads:[~2009-09-11  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02  9:35 UBIFS power cut issues JiSheng Zhang
2009-09-08  6:22 ` Artem Bityutskiy
2009-09-09  9:45   ` JiSheng Zhang
2009-09-09 10:06     ` Artem Bityutskiy
2009-09-11  9:23       ` JiSheng Zhang [this message]
2009-09-10 15:42     ` Artem Bityutskiy
2009-09-10 16:00       ` Bill Gatliff
2009-09-11  8:01         ` Artem Bityutskiy
2009-09-11  9:33       ` JiSheng Zhang
2009-09-11 10:06         ` 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=2df346410909110223p87aefd2ibfe8fb11e040f56f@mail.gmail.com \
    --to=jszhang3@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.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