linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Paul-Kenji Cahier <pkc@f1-photo.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [HFS+] large drive mounting issue
Date: Thu, 24 Jan 2013 15:06:01 +0400	[thread overview]
Message-ID: <1359025561.2060.5.camel@slavad-ubuntu> (raw)
In-Reply-To: <CANw21=CVGkp7ijSJmcLEU5241JL0hNpLoxC-LJby37RzzJSSrg@mail.gmail.com>

Hi Paul-Kenji,

On Thu, 2013-01-24 at 10:48 +0000, Paul-Kenji Cahier wrote:
> Hi all,
> 
> I am running 3.2.5-gg987 and I am experiencing a problem mounting my
> 3TB HFS+ formatted drive.
> The drive has been used on a mac (and formatted there) for a long
> time. I just need RO access to it, so journaling shouldn't be an
> issue.
> 
> Regardless of my mount attempts it errors with:
> [681648.160023] hfs: invalid secondary volume header
> [681648.160026] hfs: unable to find HFS+ superblock
> 
> 
> Here's the drive info:
> $ sudo parted /dev/sdb unit B print
> Model: ATA WDC WD30EZRX-00D (scsi)
> Disk /dev/sdb: 3000592982016B
> Sector size (logical/physical): 512B/4096B
> Partition Table: gpt
> 
> Number Start End Size File system Name Flags
> 1 20480B 209735679B 209715200B fat32 EFI System Partition boot
> 2 209735680B 3000458743807B 3000249008128B hfs+
> 3TB-Backup
> 
> 
> Things I've tried:
> Direct mount:
> sudo mount -t hfsplus /dev/sdb2 /testmnt
> 
> Offset mount:
> sudo mount -t hfsplus -o ro,loop,offset=209735680 /dev/sdb /testmnt
> 
> Manual loop device offset mount:
> sudo losetup -f /dev/sdb --offset 209735680 --sizelimit 3000249008128 --show
> sudo mount -t hfsplus -o loop,force,ro /dev/loop0 /testmnt
> 
> Manual loop device direct mount:
> sudo losetup /dev/sdb2 --offset 0 --sizelimit 3000249008128 --show
> sudo mount -t hfsplus -o loop,force,ro /dev/loop0 /testmnt
> 
> 
> None of this works.
> For what it's worth, the block headers are per HFS+ specification in
> the right place:
> 
> $ sudo dd if=/dev/sdb2 bs=1024 skip=1 count=1|hd|head
> 00000000 48 2b 00 04 80 00 21 00 48 46 53 4a 00 00 15 d6 |H+....!.HFSJ....|
> 00000010 cd 0e 7c 22 cd 0f 0d 10 00 00 00 00 cd 0e 6e 12 |..|"..........n.|
> 
> $ sudo dd if=/dev/sdb2 bs=1024 skip=$((3000249008128/1024-1)) count=1|hd|head
> 00000000 48 2b 00 04 80 00 21 00 31 30 2e 30 00 00 15 d6 |H+....!.10.0....|
> 00000010 cd 0e 7c 22 cd 0e 6e 12 00 00 00 00 cd 0e 6e 12 |..|"..n.......n.|
> 

Thank you for detailed report.

I think that it is a not valid calculation of secondary volume header
placement in driver code. I will check this presupposition.

Could you enable DBG masks (please, see hfsplus_fs.h), recompile kernel
and try to mount again? Could you share debug output in the system log
with enabled DBG masks?

Thanks,
Vyacheslav Dubeyko. 

> Thanks,
> 
> -fcpk/Paul-Kenji
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2013-01-24 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 10:48 [HFS+] large drive mounting issue Paul-Kenji Cahier
2013-01-24 11:06 ` Vyacheslav Dubeyko [this message]
2013-01-24 11:18 ` Vyacheslav Dubeyko

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=1359025561.2060.5.camel@slavad-ubuntu \
    --to=slava@dubeyko.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pkc@f1-photo.com \
    /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;
as well as URLs for NNTP newsgroup(s).