From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: raid-0/reiserfs problem; file system not recognized after reboot
Date: Thu, 30 Jan 2003 13:42:24 +0100 [thread overview]
Message-ID: <20030130124224.GA8844@middle.of.nowhere> (raw)
I have a problem with raid-0 and reiserfs in linux-2.4.21-pre3-ac5 on
Debian/Testing.
When I create two raid-0 partitions with this script:
umount /dev/md0
umount /dev/md1
raidstop /dev/md0
raidstop /dev/md1
dd if=/dev/zero of=/dev/hdi bs=512 count=1
dd if=/dev/zero of=/dev/hdk bs=512 count=1
fdisk /dev/hdi < /root/fdisk.in
fdisk /dev/hdk < /root/fdisk.in
mkraid --really-force /dev/md0
mkraid --really-force /dev/md1
yes | mkreiserfs /dev/md0
yes | mkreiserfs /dev/md
with fdisk.in like this:
n
p
1
140000
t
fd
n
p
2
t
2
fd
w
p
q
and the partitions like this:
Disk /dev/hdi: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdi1 1 140000 70559968+ fd Linux raid autodetect
/dev/hdi2 140001 155061 7590744 fd Linux raid autodetect
Disk /dev/hdk: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdk1 1 140000 70559968+ fd Linux raid autodetect
/dev/hdk2 140001 155061 7590744 fd Linux raid autodetect
I can mount both /dev/md0 and /dev/md1 without any trouble.
After a reboot, I see this:
:mount /dev/md1 /space6
reiserfs: checking transaction log (device 09:01) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
:mount /dev/md0 /space5
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 09:00.
mount: you must specify the filesystem type
:mount -t reiserfs /dev/md0 /space5
read_super_block: can't find a reiserfs filesystem on (dev 09:00, block 128, size 512)
read_super_block: can't find a reiserfs filesystem on (dev 09:00, block 16, size 512)
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
:r /proc/mdstat
Personalities : [raid0]
read_ahead 1024 sectors
md1 : active raid0 hdi1[0] hdk1[1]
141119744 blocks 64k chunks
md0 : active raid0 hdi[0] hdk[1]
156301312 blocks 64k chunks
unused devices: <none>
I searched google (www/usenet) and didn't find any hints. I'm not
mounting the partitions from fstab, so the raid process is started at
the correct time.
Can anybody point me to the error I'm making?
Thanks,
Jurriaan
--
HORROR FILM WISDOM:
1. When it seems that you've killed the monster, never check to see if
it's really dead.
GNU/Linux 2.4.21-pre3-ac5 SMP/ReiserFS 1x2824 bogomips load av: 0.29 0.61 0.31
next reply other threads:[~2003-01-30 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 12:42 Jurriaan [this message]
[not found] ` <20030130130041.GA21637@codemonkey.org.uk>
2003-01-30 13:30 ` raid-0/reiserfs problem; file system not recognized after reboot Jurriaan
2003-01-30 15:00 ` [SOLVED!] " Jurriaan
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=20030130124224.GA8844@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@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