| Summary: | btrfs not identified in fstab and mcc | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pierre Jarillon <jarillon> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | thierry.vignaud |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | report.bug | ||
|
Description
Pierre Jarillon
2014-12-05 16:43:32 CET
What generated your /etc/fstab? CC:
(none) =>
thierry.vignaud
Thierry Vignaud
2014-12-08 17:20:41 CET
Keywords:
(none) =>
NEEDINFO I have installed Mageia 5 alpha2 and it has been updated at least 3 time each week until now. To be accurate Mga 5 alpha2 x86_64 from a DVD. And you created the btrfs fs at install time? Please attach your /root/drakx/report.bug.xz > And you created the btrfs fs at install time?
No! I have first installed alpha2 with 2 disks without any btrfs. This was done few days after the availability of alpha2. Few days ago, I have intalled a third new unformatted disk (Segate 1 TB), I made 3 partitions (swap and 2 btrfs) with MCC.
I had to remove this disk to replace another which was defective.
To do this I have commented fstab, and I have seen ext2:
# Entry for /dev/sda1 :
UUID=edf3868e-be68-4f05-ab1b-9cb19b2df967 / ext4 relatime,acl 1 1
# Entry for /dev/sdb6 :
UUID=ca1bcff4-d30e-4b1d-91ca-fbc6a455621f /home1 reiserfs relatime,user_xattr,notail 1 2
# Entry for /dev/sda6 :
UUID=3d1c741c-4ca6-49d6-b1eb-284a9bfa5e95 /home2 reiserfs user_xattr,relatime,notail 1 2
# Entry for /dev/sdb6 :
#UUID=7fcd3f4d-b17f-4db8-be7b-7a9bd4eb0719 /home3 ext2 defaults 1 2
# Entry for /dev/sdb1 :
UUID=31668834-8288-43be-800c-f8fcce7a4570 /mga4 ext4 relatime,acl 1 2
# Entry for /dev/sdb1 :
#UUID=bd1a0806-fb10-40c0-a74c-5c7765ec3cb2 /mga5 ext2 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
UUID=6240e08f-87f0-4cd2-8eb2-3d0f83461545 swap swap defaults 0 0
# Entry for /dev/sdb5 :
#UUID=4e46296b-9d2c-44dd-bd7c-1a2f33ae1a5d swap swap defaults 0 0
Now I must to buy another disk and try again. I don't know if I made a mistake twice, if diskdrake made and error and create ext2 instead of btrfs or if btrfs is shown a ext2.
In report.bug dracut said that the command 'btrfs' could not be found. A beginning of explanation?
Please, wait for I retry a new with disk.
How a btrfs must be reported in fstab, fdisk and diskdrake?
Created attachment 5693 [details]
report.bug
Report.bug.xy from Mageia 5 beta as requested.
I have found how to reproduce the problem. 1- With MCC/Disdrake, I create some partitions btrfs. I don't format them and I quit. The partion table is written on the disk. A warning tell me that the mounting points wil be lost. 2- I come back to diskdrake, the partitions are still there, but shown as Linux native. 3- I format the partition, ext2 is used . If this is not a bug, but a feature, a warning must tell that the type of file system also will be lost. ID in partitation table only says it's linux or swap, there's no specific ids for all possible fses. So if you don't format your partition, there's no way to tell it's btrfs. And anyway it's not since at this point it's not formatted. Priority:
Normal =>
Low |