udisks mounts filesystems sdb1, sdb3 but misses out sdb2 saying unknown filesystem type 'reiserfs'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: udisks
Running Ubuntu Lucid beta1 and observing some strange behaviour in the automounting
of partitions of type reiserfs.
In short I have a 16GB SD card which has 3 reiserfs partitions and mounted just fine
up until todays updates (31 March) which included updates to dbus and hal.
: #root@amd754n(
Wed Mar 31 15:36:48 BST 2010
dbus_1.
dbus-x11_
hal_0.5.
libdbus-
libhal1_
libhal-
libkephal4_
After applying the updates instead of successfully mounting all 3 reiserfs sdb1, sdb2, sdb3,
my system instead mounted sdb1 and sdb3 and skipped over sdb2 giving graphical dialog box message:
Error mounting: mount: unknown filesystem type 'reiserfs' Screenshot ( http://
Screenshot long URL ( http://
Nothing much from a websearch:
http://
Here is the log output showing the problem behaviour:
r 31 14:08:03 amd754n kernel: [ 5255.609386] USB Mass Storage support registered.
Mar 31 14:08:08 amd754n kernel: [ 5260.610319] scsi 6:0:0:0: Direct-Access Generic STORAGE DEVICE 9802 PQ: 0 ANSI: 0
Mar 31 14:08:08 amd754n kernel: [ 5260.611323] sd 6:0:0:0: Attached scsi generic sg2 type 0
Mar 31 14:08:09 amd754n kernel: [ 5260.857912] sd 6:0:0:0: [sdb] 31388672 512-byte logical blocks: (16.0 GB/14.9 GiB)
Mar 31 14:08:09 amd754n kernel: [ 5260.859021] sd 6:0:0:0: [sdb] Write Protect is off
Mar 31 14:08:09 amd754n kernel: [ 5260.865783] sdb: sdb1 sdb2 sdb3
Mar 31 14:08:09 amd754n kernel: [ 5260.872565] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Mar 31 14:08:15 amd754n kernel: [ 5266.954957] REISERFS (device sdb1): found reiserfs format "3.6" with standard journal
Mar 31 14:08:15 amd754n kernel: [ 5266.954976] REISERFS (device sdb1): using ordered data mode
Mar 31 14:08:15 amd754n kernel: [ 5266.955845] REISERFS (device sdb1): journal params: device sdb1, size 8192, journal first b
lock 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 31 14:08:15 amd754n kernel: [ 5266.957031] REISERFS (device sdb1): checking transaction log (sdb1)
Mar 31 14:08:15 amd754n kernel: [ 5267.180152] REISERFS (device sdb1): Using r5 hash to sort names
Mar 31 14:08:15 amd754n kernel: [ 5267.213204] REISERFS (device sdb3): found reiserfs format "3.6" with standard journal
Mar 31 14:08:15 amd754n kernel: [ 5267.213230] REISERFS (device sdb3): using ordered data mode
Mar 31 14:08:15 amd754n kernel: [ 5267.214085] REISERFS (device sdb3): journal params: device sdb3, size 8192, journal first b
lock 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 31 14:08:15 amd754n kernel: [ 5267.215222] REISERFS (device sdb3): checking transaction log (sdb3)
Mar 31 14:08:15 amd754n kernel: [ 5267.220587] REISERFS (device sdb3): Using r5 hash to sort names
Mar 31 14:13:34 amd754n sudo: pam_sm_
Mar 31 14:13:34 amd754n sudo: pam_sm_
Mar 31 14:13:34 amd754n sudo: pam_sm_
: #root@amd754n(~) ;date;uname -a
Wed Mar 31 14:17:32 BST 2010
Linux amd754n 2.6.32-17-generic #26-Ubuntu SMP Fri Mar 19 23:58:53 UTC 2010 i686 GNU/Linux
: #root@amd754n(~) ;apt-cache policy udisks
udisks:
Installed: 1.0.0+git201003
Candidate: 1.0.0+git201003
Version table:
*** 1.0.0+git201003
500 http://
100 /var/lib/
Here is what it should look like (/var/log/messages few days ago 28th March):
Mar 28 12:43:40 amd754n slim: pam_sm_
Mar 28 12:43:40 amd754n slim: Passphrase file wrapped
Mar 28 12:43:58 amd754n kernel: [ 132.808290] REISERFS (device sdb2): found reiserfs format "3.6" with standard journal
Mar 28 12:43:58 amd754n kernel: [ 132.808312] REISERFS (device sdb2): using ordered data mode
Mar 28 12:43:58 amd754n kernel: [ 132.809286] REISERFS (device sdb2): journal params: device sdb2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 28 12:43:58 amd754n kernel: [ 132.810522] REISERFS (device sdb2): checking transaction log (sdb2)
Mar 28 12:43:58 amd754n kernel: [ 132.816146] REISERFS (device sdb2): Using r5 hash to sort names
Mar 28 12:43:58 amd754n kernel: [ 132.977538] REISERFS (device sdb1): found reiserfs format "3.6" with standard journal
Mar 28 12:43:58 amd754n kernel: [ 132.977574] REISERFS (device sdb1): using ordered data mode
Mar 28 12:43:58 amd754n kernel: [ 132.978544] REISERFS (device sdb1): journal params: device sdb1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 28 12:43:58 amd754n kernel: [ 132.979806] REISERFS (device sdb1): checking transaction log (sdb1)
Mar 28 12:43:58 amd754n kernel: [ 132.984893] REISERFS (device sdb1): Using r5 hash to sort names
Mar 28 12:43:59 amd754n kernel: [ 133.141904] REISERFS (device sdb3): found reiserfs format "3.6" with standard journal
Mar 28 12:43:59 amd754n kernel: [ 133.141944] REISERFS (device sdb3): using ordered data mode
Mar 28 12:43:59 amd754n kernel: [ 133.142917] REISERFS (device sdb3): journal params: device sdb3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 28 12:43:59 amd754n kernel: [ 133.144194] REISERFS (device sdb3): checking transaction log (sdb3)
Mar 28 12:43:59 amd754n kernel: [ 133.160574] REISERFS (device sdb3): Using r5 hash to sort names
Just to check that I sdb2 really is reiserfs I did an fsck.reiserfs /dev/sdb2 which can be seen in the attached text output.
Here is some perhaps relevant mount information:
: #root@amd754n(~) ;mount | fgrep sdb
/dev/sdb1 on /media/py2010 type reiserfs (rw,nosuid,
/dev/sdb3 on /media/kjeller10 type reiserfs (rw,nosuid,
My best guess about this bug is that udisks contains an error message which is inappropriate - udisks seems to happily recognise reiserfs, or alternatively perhaps there is another mount daemon operating and it is this mount daemon rather than udisks which is giving the graphical dialog in the screenshot ( http://
Also in the attached text output is a failed attempt to use parted /dev/sdb which core dumped after giving message
"device-mapper: deps ioctl failed: No such device or address" and showing Segmentation fault (core dumped)
root@amd754n(~) ;apt-cache policy parted
parted:
Installed: 2.2-1ubuntu4
Candidate: 2.2-1ubuntu4
Version table:
*** 2.2-1ubuntu4 0
500 http://
100 /var/lib/
I wasn't sure whether to file another bug for parted in launchpad, or to follow the onscreen instructions and go to
gnu.org site looking for version 2.2 [ Your report should contain the version of this release (2.2) ]
This bug, I suspect, was only there for a short time while things changed rapidly between beta releases of Lucid.
I use Debian Squeeze as my main desktop now, although Ubuntu Lucid is there also on dual boot, so unless this is
an issue for anyone else, then seems no point in keeping this bug open long term.
Suggest this bug is removed from the list of active bugs by janitor or next bug clearout.