| Summary: | LVM failed to mount after fdisk | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Muzi <muzammel.linux> |
| Component: | device-mapper | Assignee: | Orphan Owner <extras-orphan> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | agk, bmarzins, dwysocha, extras-orphan, heinzm, jonathan, kzak, prockai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 13:15:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
I have now solve this issue, but i think/consider bug in fdisk not to set Start value 1, need to set it manually & its working f9 now. during fdisk, remove/create partition. switch to expert mode. and choose option b Command (m for help): x Expert command (m for help): m Command action b move beginning of data in a partition Partition number (1-4): 1 New beginning of data (1-20971519, default 2048): 63 Now select 63, which means Start value =1 in terms of cylinders. Now save and quit fdisk. Now verify using below fdisk command, you see start value =1 in terms of cylinder fdisk -l -u=cylinders /dev/vmdata/vm7.var Device Boot Start End Blocks Id System /dev/vmdata/vm7.var1 1 11530 10485728+ 83 Linux Also below, you see Start value = 63 in terms of sectors fdisk -l /dev/vmdata/vm7.var Device Boot Start End Blocks Id System /dev/vmdata/vm7.root1 63 20971519 10485728+ 83 Linux If we not manually set Start value then fdisk by default assing value = 2 in terms of cylinder, so i think its bug in fdisk who not the set the right start value . Why do you care about cylinders? The default is to use sectors, the CHS addressing is obsolete legacy used by MS-DOS. CHS is completely irrelevant for Linux. The current default is to use 1MiB offset (2048 sectors) for the first partition, because this value is usable for all mainstream operation systems and block devices. Ok, leave cylinders, i mention cylinders only to explain the issue, problem is fdisk set the start value (2048) which is not working, when its set to 63 then its working, why this happen then ? when i try to mount this lvm after fdisk part it gives below error in messages log. EXT3-fs (dm-33): error: can't find ext3 filesystem on dev dm-33 EXT2-fs (dm-33): error: can't find an ext2 filesystem on dev dm-33 But when i set the start value = 63, its start working/Ok. Thanks Muzi Can you test it ? i think its bug and need to be fix. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Description of problem: fdisk reset automatically the default values of heads/sectors after adding an partition. Version-Release number of selected component (if applicable): 2.18-4.8 How reproducible: Steps to Reproduce: 1. Create Logical Volume Like lvcreate -L 10G -n vm7.var vmdata 2. Resize Logical Volume. to add more space lvresize -L 15G /dev/vmdata/vm7.var 3. fdisk /dev/vmdata/vm7.var delete partition by Pressing -> d create new partition by Pressing -> n Select Primary Partition by pressing -> p First sector (2048-31457279, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-31457279, default 31457279): Using default value 31457279 Press w and save Actual results: [root@mysystem ~]# fdisk -l -u=cylinders /dev/vmdata/vm7.var Disk /dev/vmdata/vm7.var: 16.1 GB, 16106127360 bytes 32 heads, 57 sectors/track, 17246 cylinders Units = cylinders of 1824 * 512 = 933888 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00005d8a Device Boot Start End Blocks Id System /dev/vmdata/vm7.var1 2 17247 15727616 83 Linux Expected results: [root@mysystem ~]# fdisk -l -u=cylinders /dev/vmdata/vm7.var Disk /dev/vmdata/vm7.var: 16.1 GB, 16106127360 bytes 255 heads, 63 sectors/track, 17246 cylinders Units = cylinders of 1824 * 512 = 933888 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00005d8a Device Boot Start End Blocks Id System /dev/vmdata/vm7.var1 1 17247 15727616 83 Linux Additional info: As values in actual resutls, heads and sectors/track values are changed. Its not 255(head) and 63(sectors), also Start value = 2, its must be 1. when i try to mount this lvm after fdisk part it gives below error in messages log. EXT3-fs (dm-33): error: can't find ext3 filesystem on dev dm-33 EXT2-fs (dm-33): error: can't find an ext2 filesystem on dev dm-33 Values are not come fine after fdisk. Please Suggest.