From: Sergei Poselenov <sposelenov@emcraft.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS: file data corruption during the power cut-off test
Date: Fri, 7 Jun 2019 17:23:55 +0300 [thread overview]
Message-ID: <20190607172355.6541fa51@sergmir.emcraft.com> (raw)
In-Reply-To: <CAFLxGvy1BTuLkcn=7N=FG_q5cBgj5L1YzyhiakVFewYPyr6dzA@mail.gmail.com>
Hello Richard,
On Thu, 6 Jun 2019 20:13:07 +0200 Richard Weinberger <richard.weinberger@gmail.com> wrote:
> On Thu, Jun 6, 2019 at 8:08 PM Sergei Poselenov <sposelenov@emcraft.com> wrote:
> > This is understood. However, on the file length that is written to the partition, I'd expect that the file content will be the same as in the original file. This is not so.
> > Is it expected, or is it a deficiency of UBI?
>
> Please show in detail what you are doing, on syscall level, and what
> the expected output is.
>
Here is my test:
/mnt/data1 # for i in `seq 0 99`; do
> dd if=/bin/busybox of=test${i}; done
During the test, the board is powered off.
After bootup:
/mnt/data1 # ls -l
-rw-r--r-- 1 root root 396795 Jan 8 23:58 test0
-rw-r--r-- 1 root root 396795 Jan 8 23:58 test1
-rw-r--r-- 1 root root 113664 Jan 8 23:58 test2
/mnt/data1 #
/mnt/data1 # md5sum /bin/busybox *
23376319de62934c3859615e6244aae0 /bin/busybox
23376319de62934c3859615e6244aae0 test0
23376319de62934c3859615e6244aae0 test1
87cd1d1a28896e63eb039d75efef43a3 test2
As expected, test2 is shorter, hence has a different checksum.
Now, I' overwriting the content of the "test0" with "test2", without "test0" truncation:
mnt/data1 # dd if=test2 of=test0 conv=notrunc
222+0 records in
222+0 records out
113664 bytes (111.0KB) copied, 0.859668 seconds, 129.1KB/s
/mnt/data1 # md5sum *
23376319de62934c3859615e6244aae0 test0
23376319de62934c3859615e6244aae0 test1
87cd1d1a28896e63eb039d75efef43a3 test2
/mnt/data1 #
For this particular test pass, the content of test2 matches the content of the original file test0, so overwriting test0 with test2 doesn't change the data.
However, upon retry of the very same test from the beginning (with the power cut-off in the middle) it's easily to have the content of test2 (exactly the last 512 bytes in my case) which doesn't match test0, so "dd if=test2 of=test0 conv=notrunc" will result in test0 with a different checksum.
To remind, the partition is mounted with the "sync" option.
Thanks!
Regards,
Sergei
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-06-07 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 9:10 UBIFS: file data corruption during the power cut-off test Sergei Poselenov
2019-06-06 14:55 ` Richard Weinberger
2019-06-06 18:08 ` Sergei Poselenov
2019-06-06 18:13 ` Richard Weinberger
2019-06-07 14:23 ` Sergei Poselenov [this message]
2019-06-07 16:01 ` Steve deRosier
2019-06-09 8:32 ` Sergei Poselenov
2019-06-09 15:25 ` Steve deRosier
2019-06-07 16:02 ` Richard Weinberger
2019-06-08 6:42 ` Sergei Poselenov
2019-06-08 8:46 ` Richard Weinberger
2019-06-09 8:18 ` Sergei Poselenov
2019-06-09 8:53 ` Richard Weinberger
2019-06-09 9:59 ` Sergei Poselenov
2019-06-09 10:00 ` Richard Weinberger
2019-06-15 7:26 ` Sergei Poselenov
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=20190607172355.6541fa51@sergmir.emcraft.com \
--to=sposelenov@emcraft.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox