Bug 547994
| Summary: | Logical Volume Management: Parse Error | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Runwalsoft <m_runwal> | ||||||||
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 12 | CC: | agk, bmarzins, bmr, dwysocha, heinzm, lvm-team, mbroz, m_runwal, msnitzer, prajnoha, prockai | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2010-05-11 13:15:45 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Did you edit /etc/lvm/lvm.conf? Please, attach this file too. Thanks. (..or better try running "lvmdump" if possible and attach the file here) Output of lvmdump ---------- [Manish@runwalsoft Documents]$ su - Password: [root@runwalsoft ~]# lvmdump Could not run lvm binary 'lvm' [root@runwalsoft ~]# whereis lvmdump lvmdump: /sbin/lvmdump /usr/share/man/man8/lvmdump.8.gz You have mail in /var/spool/mail/root [root@runwalsoft ~]# cd /sbin/lvmdump -bash: cd: /sbin/lvmdump: Not a directory [root@runwalsoft ~]# cd /sbin/ [root@runwalsoft sbin]# lvmdump Could not run lvm binary 'lvm' [root@runwalsoft sbin]# ------------- And Attached in lvm.conf Created attachment 378890 [details]
lvm.conf
(In reply to comment #3) > Output of lvmdump > ---------- > [Manish@runwalsoft Documents]$ su - > Password: > [root@runwalsoft ~]# lvmdump > Could not run lvm binary 'lvm' Oh.. could you please gather the files manually then - I would need the whole contents of "/etc/lvm" dir (..pack it it one file, please). Also, the output of "rpm -qa device-mapper*" and "rpm -qa lvm2*". Thanks. # rpm -qa device-mapper* device-mapper-devel-1.02.38-2.fc12.i686 device-mapper-event-1.02.38-2.fc12.i686 device-mapper-event-libs-1.02.38-2.fc12.i686 device-mapper-multipath-0.4.9-5.fc12.i686 device-mapper-libs-1.02.38-2.fc12.i686 device-mapper-multipath-libs-0.4.9-5.fc12.i686 device-mapper-1.02.38-2.fc12.i686 # rpm -qa lvm2* lvm2-libs-2.02.53-2.fc12.i686 lvm2-2.02.53-2.fc12.i686 attached zip files of lvm Created attachment 378977 [details] All lvm files and folders. Please note that I was running fedora 10 at start working. Then upgraded fedora 11. and within 2 week I upgraded F12. and its being few weeks that I am using F12. I am not sure whether its being concern with another bug which I am facing. https://bugzilla.redhat.com/show_bug.cgi?id=544935 As I am just trying to help and get resolve issue. Hmm, there's a problematic character sequence in the /etc/lvm/cache/.cache line that causes the problem - the "^@": /dev/di^@k/by-uu^@d/2d6d5^@36-84a0^@461f-a610-5f5a43a38ef5 Actually, all of these are zeroes when I looked in hexa directly... You can remove this cache file manually, it will always be recreated by lvm. But I'm wondering how this char sequence got there. Can you try to find the item in /dev directly? Do you see it garbled there, too? If yes, then this could also be some udev daemon error not creating the names properly... Anyway, it's quite interesting how did those "zeroes" get there... > [root@runwalsoft ~]# lvmdump > Could not run lvm binary 'lvm' > /dev/di^@k/by-uu^@d/2d6d5^@36-84a0^@461f-a610-5f5a43a38ef5 There is quite possible hw memory corruption btw. Is your system stable otherwise? Looks like this is fixed. As far as /dev is concern I don't see any suspicious their. but if you want to see specific thing then give me list of commands so that I will execute and provide you output. is it related with this error as well ? https://bugzilla.redhat.com/show_bug.cgi?id=544935 Thank your for your support. (In reply to comment #10) > Looks like this is fixed. Have you encountered this problem since then? After you removed the /etc/lvm/.cache file manually, has the error come into the way again? This error have been resolved. Actually broken RAM was creating the problem. once I used new RAM then its not giving me any error. so you can close this issue. OK, closing then... |
Created attachment 378723 [details] Bootlog Description of problem: Whenever I got my machine I got Setting up Logical Volume Management: Parse error at byte 135 (line 7): expected a value Version-Release number of selected component (if applicable): Fodora 12 How reproducible: For every refresh I am getting this error. Steps to Reproduce: 1. Start computer and we can see this message. 2. 3. Actual results: There should not be any error Expected results: while booting there should not be error Additional info: