RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 901697 - 'Parse error at byte 77 (line 5): unexpected token' during multiple raid volume creation
Summary: 'Parse error at byte 77 (line 5): unexpected token' during multiple raid volu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jonathan Earl Brassow
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: BrassowRHEL6Bugs
TreeView+ depends on / blocked
 
Reported: 2013-01-18 20:35 UTC by Corey Marthaler
Modified: 2014-10-14 08:24 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.107-1.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed - better error handling.
Clone Of:
Environment:
Last Closed: 2014-10-14 08:24:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1387 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2014-10-14 01:39:47 UTC

Description Corey Marthaler 2013-01-18 20:35:24 UTC 
Description of problem:
This was with lvmetad running.

./raid_sanity -t raid10 -e many_raids

SCENARIO (raid10) - [many_raids]
Recreating VG and PVs to increase metadata size
Making 500 raids...
1 hayes-01: lvcreate --type raid10 -i 2 -n 500_1 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!
2 hayes-01: lvcreate --type raid10 -i 2 -n 500_2 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!
3 hayes-01: lvcreate --type raid10 -i 2 -n 500_3 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!

[...]

198 hayes-01: lvcreate --type raid10 -i 2 -n 500_198 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!
  Internal error: Reserved memory (24588288) not enough: used 25858048. Increase activation/reserved_memory?
199 hayes-01: lvcreate --type raid10 -i 2 -n 500_199 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!
  Internal error: Reserved memory (24600576) not enough: used 25870336. Increase activation/reserved_memory?
200 hayes-01: lvcreate --type raid10 -i 2 -n 500_200 -L 15M --nosync raid_sanity
  WARNING: New raid10 won't be synchronised. Don't read what you didn't write!
  Parse error at byte 77 (line 5): unexpected token
  Volume group for uuid not found: uz8lE0H2GXuM8oBmUbHCdySUMVaSdehOQUGccXcWvu9xOMplEYCuKDQdA6spqWJ1
  Failed to activate raid_sanity/500_200_rmeta_3 for clearing
  Internal error: Reserved memory (24645632) not enough: used 74801152. Increase activation/reserved_memory?
couldn't create raid:
      hayes-01 lvcreate --type raid10 -i 2 -n 500_200 -L 15M --nosync raid_sanity


Version-Release number of selected component (if applicable):
2.6.32-354.el6.x86_64
lvm2-2.02.98-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
lvm2-libs-2.02.98-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
lvm2-cluster-2.02.98-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
udev-147-2.43.el6    BUILT: Thu Oct 11 05:59:38 CDT 2012
device-mapper-1.02.77-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
device-mapper-libs-1.02.77-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
device-mapper-event-1.02.77-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
device-mapper-event-libs-1.02.77-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
cmirror-2.02.98-8.el6    BUILT: Wed Jan 16 07:57:25 CST 2013
Comment 1 Jonathan Earl Brassow 2013-01-23 17:55:06 UTC 
Does this happen under other kinds of LVs?

(It may happen quicker under RAID LVs because they involve more sub-LVs then other segment types, but the bug may not have anything to do with RAID.)
Comment 2 Petr Rockai 2013-01-28 11:42:39 UTC 
If this can be reproduced with lvmetad running with -f -l wire, that output would be probably quite helpful. Also, client-side logs could help. In the meantime, I'm trying to reproduce locally.
Comment 5 Jonathan Earl Brassow 2014-04-03 22:27:01 UTC 
Error message now goes something like this:

  Rounding size (25 extents) up to stripe boundary size (28 extents).
  WARNING: New raid5 won't be synchronised. Don't read what you didn't write!
  Logical volume "lv93" created

  Rounding size (25 extents) up to stripe boundary size (28 extents).
  WARNING: New raid5 won't be synchronised. Don't read what you didn't write!
  VG vg metadata too large for circular buffer

I think this is an acceptable message now, right?
Comment 6 Corey Marthaler 2014-04-07 15:56:45 UTC 
Yeah, that sounds fine now.
Comment 7 Jonathan Earl Brassow 2014-04-07 16:56:29 UTC 
Ok, I've not identified the commit that has changed this, but it should be in the next build.  I'm putting in POST.  We'll verify the message has changed once a build is done and this moves to MODIFIED.
Comment 10 Nenad Peric 2014-08-11 07:38:22 UTC 
I tested the many_raid creation and could not encounter the issue reported. 

However, there is one question/inconsistency which occurred:


Deactivating raid 500_3... and removing
2
perform raid scrubbing (lvchange --syncaction repair) on raid raid_sanity/500_2
Waiting until all mirror|raid volumes become fully syncd...
   1/1 mirror(s) are fully synced: ( 100.00% )

Deactivating raid 500_2... and removing
1
perform raid scrubbing (lvchange --syncaction check) on raid raid_sanity/500_1
Waiting until all mirror|raid volumes become fully syncd...
   1/1 mirror(s) are fully synced: ( 100.00% )


Some of these raid LVs being removed would report that syncaction check is needed and others syncaction repair. Is this a feature and what causes the different messages to be displayed? All of the LVs were created the same and no FS was made on top, so I am just curious why some need only check and the others repair.
Comment 11 Corey Marthaler 2014-08-11 15:56:14 UTC 
The "perform raid scrubbing (lvchange --syncaction check) on raid" messages are from raid_sanity which is randomly runing either '--syncaction repair || check' on every raid volume before it's deleted to check for any problems.
Comment 12 Nenad Peric 2014-08-12 07:39:03 UTC 
Ehmm.. Ok then :)
Did not occur to me to check the test code.
Comment 13 Nenad Peric 2014-08-12 15:04:41 UTC 
Marking this bug as VERIFIED. 
Did not encounter any of the issues described in the bug wile running multiple iterations of raid_sanity. 
Tested with:

lvm2-2.02.109-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
lvm2-libs-2.02.109-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
lvm2-cluster-2.02.109-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
udev-147-2.57.el6    BUILT: Thu Jul 24 15:48:47 CEST 2014
device-mapper-1.02.88-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
device-mapper-libs-1.02.88-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
device-mapper-event-1.02.88-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
device-mapper-event-libs-1.02.88-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
device-mapper-persistent-data-0.3.2-1.el6    BUILT: Fri Apr  4 15:43:06 CEST 2014
cmirror-2.02.109-1.el6    BUILT: Tue Aug  5 17:36:23 CEST 2014
Comment 14 errata-xmlrpc 2014-10-14 08:24:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1387.html
Note You need to log in before you can comment on or make changes to this bug.