Linux filesystem development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: zeroes read back more often than appended
Date: 21 Oct 2003 12:44:54 -0600	[thread overview]
Message-ID: <1066761894.3350.100.camel@patehci2> (raw)
In-Reply-To: <1066754816.12021.1.camel@patehci2>

Yes I can confirm.

Try appending nonzero to multiple files in a round robin sequence, and
udf.ko reads back zero in place of the nonzero written.  mkfs in place
of mkudffs reads back only the nonzero written.

CONFIG_SMP is not set.  CONFIG_PREEMPT is not set.  I did tell dd to
write all the backing store without skipping over any of it.

Changing those variables does fix the "width x height" test case of one
file, but not the "width x height x depth" test case of multiple files.

In particular I tried:

fswhd 0 768 mkudffs 0xFF600 0xC8 0x3
fswhd 0 768 mkudffs 0xFF600 0xC8 0x1
fswhd 0 768 mkudffs 0xFF600 0xC8 0x2

That sequence actually took down my kernel once, but for me that trouble
did not repeat.  I do not yet know where to go to begin learning how to
see the dmesg leading up to an oops.  oops kill my remote ssh.

Pat LaVarre

P.S. tty logs follow.  Two files with mkudffs, reads zeroes from both
files ouch.  One file with mkudffs, ok because of CONFIG = PREEMPT =
off.  Two files with mkfs in place of mkudffs, ok.

$
$ cd /mnt/hda11
$
$ fswhd 0 768 mkudffs 0xFF600 0xC8 0x2
Linux 2.6.0.8-udf i686
/mnt/hda11
dd if=/dev/zero of=dd.bin bs=1M seek=0 count=768 2>/dev/null
-rw-rw-r--    1 pat      pat      805306368 Oct 21 11:49 dd.bin
mkudffs 1.0.0b2 for UDF FS 1.0.0-cvs, 2002/02/09
0
hexdump -C whd0.bin | head -3
00000000  aa aa aa aa aa aa aa aa  aa aa aa aa aa aa aa aa  |................|
*
06fbe000  00 00 00 00 00 00 00 00  aa aa aa aa aa aa aa aa  |................|
hexdump -C whd1.bin | head -3
00000000  aa aa aa aa aa aa aa aa  aa aa aa aa aa aa aa aa  |................|
*
06ebb000  00 00 00 00 00 00 00 00  aa aa aa aa aa aa aa aa  |................|
+++ 2.dmesg     2003-10-21 11:50:13.486227568 -0600
+ already set
+UDF-fs DEBUG fs/udf/balloc.c:192:udf_bitmap_free_blocks: bit 15865 already set
+UDF-fs DEBUG fs/udf/balloc.c:193:udf_bitmap_free_blocks: byte= 2
+UDF-fs DEBUG fs/udf/balloc.c:192:udf_bitmap_free_blocks: bit 15865 already set
$
$ fswhd 0 768 mkudffs 0xFF600 0xC8 0x1
Linux 2.6.0.8-udf i686
/mnt/hda11
dd if=/dev/zero of=dd.bin bs=1M seek=0 count=768 2>/dev/null
-rw-rw-r--    1 pat      pat      805306368 Oct 21 11:46 dd.bin
mkudffs 1.0.0b2 for UDF FS 1.0.0-cvs, 2002/02/09
0
hexdump -C whd0.bin | head -3
00000000  aa aa aa aa aa aa aa aa  aa aa aa aa aa aa aa aa  |................|
*
0c783000
$
$ fswhd 0 768 mkfs 0xFF600 0xC8 0x2
Linux 2.6.0.8-udf i686
/mnt/hda11
dd if=/dev/zero of=dd.bin bs=1M seek=0 count=768 2>/dev/null
-rw-rw-r--    1 pat      pat      805306368 Oct 21 11:52 dd.bin
Usage: mkfs [-V] [-t fstype] [fs-options] device [size]
mke2fs 1.32 (09-Nov-2002)
0
hexdump -C whd0.bin | head -3
00000000  aa aa aa aa aa aa aa aa  aa aa aa aa aa aa aa aa  |................|
*
0c783000
hexdump -C whd1.bin | head -3
00000000  aa aa aa aa aa aa aa aa  aa aa aa aa aa aa aa aa  |................|
*
0c783000
$



  reply	other threads:[~2003-10-21 18:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 19:02 zeroes read back more often than appended Pat LaVarre
2003-10-07 20:54 ` Pat LaVarre
2003-10-08  3:49 ` Ben Fennema
2003-10-08 16:41   ` Pat LaVarre
2003-10-08 16:47     ` editable udf metadata Pat LaVarre
2003-10-08 17:51       ` Pat LaVarre
2003-10-08 18:09         ` big-endian udfct_1_0r2 Pat LaVarre
2003-10-08 18:30           ` Matthew Wilcox
     [not found]             ` <3F8472FE.9040403@lougher.demon.co.uk>
2003-10-08 19:49               ` Matthew Wilcox
2003-10-08 20:43             ` Phillip Lougher
2003-10-21 21:54         ` editable udf metadata Pat LaVarre
2003-10-21 23:17           ` Pat LaVarre
2003-10-23 16:06             ` Pat LaVarre
2003-10-24 21:40               ` Pat LaVarre
2003-10-22  8:15           ` same page access Mark B
2003-10-22 11:21             ` Matthew Wilcox
2003-10-22 17:09               ` Mark B
2003-10-22 17:10                 ` Matthew Wilcox
2003-10-08 17:02     ` zeroes read back more often than appended Pat LaVarre
2003-10-08 17:06       ` toggling smp clears x86_mce_p4thermal of make xconfig Pat LaVarre
2003-10-08 17:21     ` zeroes read back more often than appended Pat LaVarre
2003-10-08 16:46   ` soft trace of read/write of drivers/block/loop.c Pat LaVarre
2003-10-08 20:32   ` zeroes read back more often than appended Pat LaVarre
2003-10-09 20:54   ` Pat LaVarre
2003-10-10  0:52     ` Pat LaVarre
2003-10-10 16:39       ` Pat LaVarre
2003-10-10 18:15         ` Pat LaVarre
2003-10-14  0:38           ` Pat LaVarre
2003-10-14  1:48             ` Pat LaVarre
2003-10-20 23:20               ` Pat LaVarre
2003-10-21 14:47                 ` Pat LaVarre
2003-10-21 16:46                   ` Pat LaVarre
2003-10-21 18:44                     ` Pat LaVarre [this message]
2003-10-23 18:52                     ` Pat LaVarre
2003-10-27 21:55                       ` Pat LaVarre
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 16:41 Pat LaVarre
2003-11-27  0:45 ` Pat LaVarre
2003-11-28 18:20   ` Pat LaVarre
2003-11-28 18:29     ` Pat LaVarre
2003-12-11 18:42 Pat LaVarre

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=1066761894.3350.100.camel@patehci2 \
    --to=p.lavarre@ieee.org \
    --cc=linux-fsdevel@vger.kernel.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