Bug 4238 - blkid fails to recognize btrfs formated fses
Summary: blkid fails to recognize btrfs formated fses
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO, Triaged
Depends on:
Blocks: 65
  Show dependency tree / graph
 
Reported: 2012-01-23 12:26 CET by Thierry Vignaud
Modified: 2013-01-10 08:53 CET (History)
1 user (show)

See Also:
Source RPM: util-linux
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thierry Vignaud 2012-01-23 12:26:17 CET 
blkid fails to recognize btrfs formated fses
This makes disdrake thinking they're ext4 and then failed to mounnt them.
Comment 1 Manuel Hiebel 2012-01-23 12:52:29 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => tmb

Comment 2 Thierry Vignaud 2012-01-23 13:58:59 CET 
BTW "mount <some_btrfs_mount_point>" will fail the same way...
Thomas Backlund 2012-02-09 16:59:18 CET

Blocks: (none) => 65

Comment 3 Marja Van Waes 2012-05-12 10:06:13 CEST 
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.
Comment 4 Marja Van Waes 2012-05-26 13:02:40 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2012-07-06 15:03:55 CEST 
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 6 roelof Wobben 2013-01-10 08:53:05 CET 
Close this as old because there is no respons in half a year.
When someone wants to reopen it please provide details as the version of
mageia

Roelof

Status: NEW => RESOLVED
CC: (none) => r.wobben
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.