| 2008-03-18 21:01:19 |
Andrew Reusch |
bug |
|
|
added bug |
| 2008-03-18 23:32:45 |
Andrew Reusch |
title |
vol_id |
vol_id reports swap instead of resierfs |
|
| 2008-03-19 00:35:06 |
Andrew Reusch |
description |
Binary package hint: volumeid
Hi,
Here's the issue:
I'm running Feisty with the latest updates.
During the boot it will come up to "Checking local filesystems" at which point it will try and do a check on /dev/sda3, which has fstab entry as follows:
# Entry for /dev/sda3 :
UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa /home reiserfs defaults 0 2
Unfortunately, upon boot, I get this (/var/log/fsck/checkfs):
Log of fsck -C -R -A -a
Tue Mar 18 13:38:16 2008
fsck 1.40-WIP (14-Nov-2006)
Failed to open the device 'UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa': No such file or directory
fsck died with exit status 8
Tue Mar 18 13:38:16 2008
----------------
At this point, it drops to a maintenence shell with a very screwy path (just /bin or something useless like that).
Running sudo blkid /dev/sda3 will report:
/dev/sda3: UUID="a1a4ee27-950c-4439-9ce8-e69b4795c5c3" TYPE="reiserfs"
Running blkid reports the correct value; running vol_id reports a swap partition with UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa
The problem was that the partition used to be a swap partition, and mkreiserfs did not overwrite the first 64 KB of the partition.
IMHO, vol_id should check for other filesystem headers first and they should override whatever swap signature found. If the swap partition was actually being used, wouldn't the use overwrite whatever filesystem header is there?
Thanks,
Andrew |
Binary package hint: volumeid
Hi,
Here's the issue:
I'm running Feisty with the latest updates.
During the boot it will come up to "Checking local filesystems" at which point it will try and do a check on /dev/sda3, which has fstab entry as follows:
# Entry for /dev/sda3 :
UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa /home reiserfs defaults 0 2
Unfortunately, upon boot, I get this (/var/log/fsck/checkfs):
Log of fsck -C -R -A -a
Tue Mar 18 13:38:16 2008
fsck 1.40-WIP (14-Nov-2006)
Failed to open the device 'UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa': No such file or directory
fsck died with exit status 8
Tue Mar 18 13:38:16 2008
----------------
At this point, it drops to a maintenence shell with a very screwy path (just /bin or something useless like that).
The problem was that the partition used to be a swap partition, and mkreiserfs did not overwrite the first 64 KB of the partition. Hence, the swapspace header was left untouched, even though at offset 0x10000 a reiserfs header was found.
Running sudo blkid /dev/sda3 will report:
/dev/sda3: UUID="a1a4ee27-950c-4439-9ce8-e69b4795c5c3" TYPE="reiserfs"
Running blkid reports the correct value; running vol_id reports a swap partition with UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa
IMHO, vol_id should check for other filesystem headers first and they should override whatever swap signature found. If the swap partition was actually being used, wouldn't the use overwrite whatever filesystem header is there?
Thanks,
Andrew |
|
| 2008-04-02 11:17:15 |
Scott James Remnant (Canonical) |
title |
vol_id reports swap instead of resierfs |
mkreiserfs does not clear metadata from previous users of the device |
|
| 2011-12-22 06:52:48 |
Clint Byrum |
reiserfsprogs (Ubuntu): importance |
Undecided |
High |
|
| 2012-01-17 07:32:01 |
Evan Peck |
summary |
mkreiserfs does not clear metadata from previous users of the device |
mkreiserfs does not clear metadata from previous device users |
|
| 2012-01-18 04:00:30 |
Evan Peck |
description |
Binary package hint: volumeid
Hi,
Here's the issue:
I'm running Feisty with the latest updates.
During the boot it will come up to "Checking local filesystems" at which point it will try and do a check on /dev/sda3, which has fstab entry as follows:
# Entry for /dev/sda3 :
UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa /home reiserfs defaults 0 2
Unfortunately, upon boot, I get this (/var/log/fsck/checkfs):
Log of fsck -C -R -A -a
Tue Mar 18 13:38:16 2008
fsck 1.40-WIP (14-Nov-2006)
Failed to open the device 'UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa': No such file or directory
fsck died with exit status 8
Tue Mar 18 13:38:16 2008
----------------
At this point, it drops to a maintenence shell with a very screwy path (just /bin or something useless like that).
The problem was that the partition used to be a swap partition, and mkreiserfs did not overwrite the first 64 KB of the partition. Hence, the swapspace header was left untouched, even though at offset 0x10000 a reiserfs header was found.
Running sudo blkid /dev/sda3 will report:
/dev/sda3: UUID="a1a4ee27-950c-4439-9ce8-e69b4795c5c3" TYPE="reiserfs"
Running blkid reports the correct value; running vol_id reports a swap partition with UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa
IMHO, vol_id should check for other filesystem headers first and they should override whatever swap signature found. If the swap partition was actually being used, wouldn't the use overwrite whatever filesystem header is there?
Thanks,
Andrew |
Binary package hint: volumeid
Hi,
Here's the issue:
I'm running Feisty with the latest updates.
During the boot it will come up to "Checking local filesystems" at which point it will try and do a check on /dev/sda3, which has fstab entry as follows:
# Entry for /dev/sda3 :
UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa /home reiserfs defaults 0 2
Unfortunately, upon boot, I get this (/var/log/fsck/checkfs):
Log of fsck -C -R -A -a
Tue Mar 18 13:38:16 2008
fsck 1.40-WIP (14-Nov-2006)
Failed to open the device 'UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa': No such file or directory
fsck died with exit status 8
Tue Mar 18 13:38:16 2008
----------------
At this point, it drops to a maintenence shell with a very screwy path (just /bin or something useless like that).
The problem was that the partition used to be a swap partition, and mkreiserfs did not overwrite the first 64 KB of the partition. Hence, the swapspace header was left untouched, even though at offset 0x10000 a reiserfs header was found.
Running sudo blkid /dev/sda3 will report:
/dev/sda3: UUID="a1a4ee27-950c-4439-9ce8-e69b4795c5c3" TYPE="reiserfs"
Running blkid reports the correct value; running vol_id reports a swap partition with UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa
IMHO, vol_id should check for other filesystem headers first and they should override whatever swap signature found. If the swap partition was actually being used, wouldn't the use overwrite whatever filesystem header is there?
TO REPRODUCE:
-format a partition (as swap)
-format it (do not clear as reiserfs)
-run vol_id (to identify partition)
-it will return type swap
Thanks,
Andrew |
|
| 2012-01-18 04:03:45 |
Evan Peck |
reiserfsprogs (Ubuntu): status |
New |
Confirmed |
|
| 2012-01-18 04:06:25 |
Evan Peck |
bug |
|
|
added subscriber Evan Peck |
