From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: hfs
Date: Thu, 04 May 2000 09:00:40 +0200 [thread overview]
Message-ID: <39112018.EFFD7A5D@wanadoo.fr> (raw)
In-Reply-To: 200005040333.XAA13971@shell.faradic.net
jingai wrote:
> I haven't tried mounting HFS cds, but I can most certainly read and write
> to HFS partiitons just fine. I don't know exactly what could be different,
> but I haven't had any troubles with it since 2.3.99x..
I confirm Scott's observations:
1. No mounting of HFS CDs. The error message (for the LinuxPPC2000 CD,
for instance) is
root[2]#mount -t hfs /dev/cdrom /mnt/cdrom/
sr.c:Bad 2K block number requested (2 1) I/O error: dev 0b:00, sector 2
hfs_fs: unable to read block 0x00000002 from dev 0b:00
hfs_fs: Unable to read superblock
sr.c:Bad 2K block number requested (0 1) I/O error: dev 0b:00, sector 0
hfs_fs: unable to read block 0x00000000 from dev 0b:00
hfs_fs: Unable to read block 0.
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted file systems
Note that this sam CD mounts perfectly with a 2.2.15-pre20 kernel.
2. Hard freeze after mounting of a HFS partition. Sometimes (I did a
couple of tests with a hfs ZIP; it's a PITA to wait 10 minutes for the
reboot with fsck each time) I can copy one or two files on the HFS
partitions, but sometimes it freezes immediately, and it freezes for
sure when I cd there and compile some little C program.
With xmon enabled, the following OOPS is captured:
bad magic 0 (should be c50c7740, creator 0), wq bug, forcing oops.
Then there follow addresses, with NIP decoded as <hfs_bnode_relse+110>
(this is defined in fs/hfs/bnode.c). All other addresses are in the
C[3-5]xxxxxx range which is not in kernel space, so I cannot decode
them. "Task" is 'cd' or 'ld' or whatever I was doing when the freeze
occurred. The oops message is generated by include/linux/wait.h.
I can see that Paul applied some changes to fs/hfs/inode.c recently, but
this doesn't change anything for me. I noted (and reported) the
brokenness of hfs at least as early as 2.3.18. I am willing to help, but
my own understanding of file systems in general, hfs in particular, and
wait queues and such stuff is too limited to get me anywhere on my own.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-04 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 3:32 Re: Re: hfs jingai
2000-05-04 7:00 ` Martin Costabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-03 22:11 hfs Dan Bethe
2000-05-20 5:54 ` hfs flar
2000-05-03 17:40 hfs Scott Knight
2000-05-03 19:31 ` hfs Michel Lanners
2000-05-03 21:03 ` hfs Martin Costabel
2000-05-03 20:26 ` hfs Scott Knight
2000-05-03 21:47 ` hfs David A. Gatwood
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=39112018.EFFD7A5D@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.