From: Seth Forshee <seth.forshee@canonical.com>
To: Christoph Hellwig <hch@tuxera.com>
Cc: Anton Salikhmetov <alexo@tuxera.com>, linux-kernel@vger.kernel.org
Subject: hfsplus mount regression in 2.6.38
Date: Wed, 25 May 2011 09:25:21 -0500 [thread overview]
Message-ID: <20110525142521.GA32511@thinkpad-t410> (raw)
We've been receiving reports of problems mounting HFS+ formatted volumes
(iPods mostly, but not exclusively) starting with the 2.6.38 kernel,
with messages like the following in dmesg.
usb 2-2: new high speed USB device using ehci_hcd and address 12
scsi7 : usb-storage 2-2:1.0
scsi 7:0:0:0: Direct-Access Apple iPod 1.62 PQ: 0 ANSI: 0
sd 7:0:0:0: Attached scsi generic sg2 type 0
sd 7:0:0:0: [sdb] 1982464 2048-byte logical blocks: (4.06 GB/3.78 GiB)
sd 7:0:0:0: [sdb] Write Protect is off
sd 7:0:0:0: [sdb] Mode Sense: 68 00 00 08
sd 7:0:0:0: [sdb] No Caching mode page present
sd 7:0:0:0: [sdb] Assuming drive cache: write through
sd 7:0:0:0: [sdb] 1982464 2048-byte logical blocks: (4.06 GB/3.78 GiB)
sd 7:0:0:0: [sdb] No Caching mode page present
sd 7:0:0:0: [sdb] Assuming drive cache: write through
sdb: [mac] sdb1 sdb2 sdb3
sd 7:0:0:0: [sdb] 1982464 2048-byte logical blocks: (4.06 GB/3.78 GiB)
sd 7:0:0:0: [sdb] No Caching mode page present
sd 7:0:0:0: [sdb] Assuming drive cache: write through
sd 7:0:0:0: [sdb] Attached SCSI removable disk
sd 7:0:0:0: [sdb] Bad block number requested
hfs: unable to find HFS+ superblock
sd 7:0:0:0: [sdb] Bad block number requested
hfs: unable to find HFS+ superblock
Reverting commits 52399b1 (hfsplus: use raw bio access for the volume
headers) and 358f26d5 (hfsplus: use raw bio access for partition tables)
fixes the problems. It appears the problems are due to hfsplus
submitting 512 byte bios to a block device whose sector size is larger
than 512 byts (2 KB in the log above), and the block driver is quite
reasonably rejecting any requests without proper sector alignment.
How would you suggest fixing this? Most file systems are using
sb_bread() for this sort of thing, but since the offending patches are
intended to stop using buffer_heads I'm assuming that's not an option.
Thanks,
Seth
next reply other threads:[~2011-05-25 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 14:25 Seth Forshee [this message]
2011-05-27 9:25 ` Christoph Hellwig
2011-05-27 13:23 ` Seth Forshee
2011-05-27 18:24 ` Seth Forshee
2011-06-02 21:58 ` Seth Forshee
2011-06-30 11:35 ` Christoph Hellwig
2011-06-30 13:10 ` Seth Forshee
2011-06-30 13:12 ` Christoph Hellwig
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=20110525142521.GA32511@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=alexo@tuxera.com \
--cc=hch@tuxera.com \
--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
all inboxes | Powered by JetHome®