linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Behrens <matt@zigg.com>
To: linux-hotplug@vger.kernel.org
Subject: LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re:
Date: Tue, 11 Nov 2008 14:29:43 +0000	[thread overview]
Message-ID: <20081111142943.GB18544@zigg.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

Hi there,

The Palm LifeDrive and T|X have a "Drive Mode" functionality that exposes
the onboard FAT32 partitions as USB drives.  However, Palm's idea of what
constitutes a FAT32 partition is a bit... weak. ;)  Below are Matthew
Garrett's insights on the filesystem probe failure from the hal list;
he suggested I get in touch with the udev developers.

I've made an image of a newly-formatted partition and posted it at
http://launchpadlibrarian.net/19129151/sdb1.img.bz2 and the Ubuntu bug
with more info can be found at
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/81219.

It's unfortunately not enough to format the partition with mkdosfs or
fsck it into compliance; the device will "fix" the partition at some
point in the future rendering it unmountable again.  (Thought you can
force-mount it with a -t vfat.)

----- Forwarded message from Matthew Garrett <mjg59@srcf.ucam.org> -----

From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Matt Behrens <matt@zigg.com>
Subject: Re: LifeDrive and T|X not seen by hal

Ok. The following things appear to be causing the failure:

1) The FAT signature in bytes 510 and 511 isn't present. This causes the 
code to bail.

2) The FAT32 signature in the fsinfo block isn't present. This causes 
the code to bail.

3) The loop looking for the root dir appears to jump out past the code 
that sets the filesystem label. This results in it ignoring the UUID 
and filesystem name.

You probably need to get in touch with the udev developers to get this 
fixed - I'm not sure which of these checks could result in false 
positives unless care is taken. Once libvolume_id is fixed hal should 
just work.

-- 
Matthew Garrett | mjg59@srcf.ucam.org
_______________________________________________
hal mailing list
hal@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal

----- End forwarded message -----

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2008-11-11 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 14:29 Matt Behrens [this message]
2008-11-11 15:40 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re: LifeDrive and T|X not seen by hal] Kay Sievers
2008-11-11 15:47 ` Matthew Garrett
2008-11-13 12:55 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Karel Zak
2008-11-13 13:40 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re: LifeDrive and T|X not seen by hal] Kay Sievers
2008-11-13 15:07 ` Kay Sievers
2008-11-13 19:01 ` Kay Sievers
2008-11-20 13:17 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Karel Zak
2008-11-20 14:50 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re: LifeDrive and T|X not seen by hal] Kay Sievers
2008-11-21  9:55 ` Kay Sievers

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=20081111142943.GB18544@zigg.com \
    --to=matt@zigg.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).