From: ASA <atris@mail.ru>
To: linux-mtd@lists.infradead.org
Subject: BLKRRPART bug in NFTL?
Date: Thu, 23 Aug 2001 16:42:42 +0400 [thread overview]
Message-ID: <1776086221.20010823164242@mail.ru> (raw)
In-Reply-To: <E15ZVks-00081M-00@pentafluge.infradead.org>
Hello all,
tried anybody to use *fdisk on DiskOnChip2000 from ramdisk
and got expected results?
I'm automating linux installation, so such thing is needed...
My system consists of:
hardware:
special embedded motherboard with AMD 486DX4-100
8 MB RAM
DiskOnChip 2000 (8 MB flash)
software:
linux kernel 2.4.1 with MTD 20010730 snapshot
root filesystem on /dev/ram0 (loaded via cmdline: initrd=inird.gz root=/dev/ram0)
All is based on debian potato (2.2; glibc 2.1; some utils, including
sfdisk, are upgraded in order to proper work with 2.4 kernel)
Symptoms are:
after executing
#deleting any partition for sanity
dd if=/dev/zero of=/dev/nftla bs=512 count=1
# BLKRRPART ioctl (reread partition information)
sfdisk -R /dev/nftla
# making 5 and 3 megs partitions on 8 MiB DOC
echo ",5000,L,*;,,L;;" | sfdisk -f /dev/nftla
# make sure partition information is reread
sfdisk -R /dev/nftla
the root filesystem (ramdisk) is screwed up!
again, after clean reboot only invoking
BLKRRPART ioctl is enough to break ramdisk
in the same configuration, operating with hard disks instead of DOC
is absolutely .
Also, to reproduce this bug in other environment (only the kernel is
the same) I tried to put my kernel (2.4.1+MTD-20010730) on the debian
installation diskette and after using cfdisk ramdisk was screwed again...
--
Best regards,
ASA mailto:atris@mail.ru
next parent reply other threads:[~2001-08-23 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15ZVks-00081M-00@pentafluge.infradead.org>
2001-08-23 12:42 ` ASA [this message]
2001-08-24 2:15 ` BLKRRPART bug in NFTL? Alexandru Harsanyi
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=1776086221.20010823164242@mail.ru \
--to=atris@mail.ru \
--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