Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 57550 - --bytes-per-inode kickstart option problem
Summary: --bytes-per-inode kickstart option problem
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Mike McLean
URL:
Whiteboard: FC4
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-15 14:13 UTC by Jarek Polok
Modified: 2007-11-30 22:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-14 20:20:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jarek Polok 2001-12-15 14:13:56 UTC
Description of Problem:

--bytes-per-inode option in kickstart install mode does not work on 
per partition basis, but globally.
In addition the last value used in per partition option is set for all
partitions having the option. 
Note that it happens ONLY in kickstart mode 


How Reproducible:

Use kickstart install file with options alike:

part /part1 [other opts] --on-disk=sda 
part /part2 [other opts] --on-disk=sdb --bytes-per-inode=266144

[I'm not sure if the same will happen if you have partitions on same disk]

Then install the system using it, check number of bytes per inode 
with dumpe2fs.

Actual Results:

/part1 and /part2 will have 266144 bytes per inode ...


Expected Results:

/part1 - default bytes-per-inode
/part2 266144 bytes-per-inode

Additional Information:

It seems that some values are not cleared in a for loop in
anaconda's sources: kickstart.py file.

Comment 1 Michael Fulbright 2002-01-16 20:40:55 UTC
Will be fixed in the next release.

Comment 2 Michael Fulbright 2002-03-26 17:30:11 UTC
Deferring to future release.

Comment 3 Brent Fox 2004-12-10 17:56:35 UTC
I'm reopening this bug because it was never fixed and I now have a
customer that is hitting this issue.

Comment 4 test 2004-12-14 20:38:10 UTC
-


Note You need to log in before you can comment on or make changes to this bug.