Bug 18552 – Usage of disk labels in fstab

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 18552 - Usage of disk labels in fstab

Summary:	Usage of disk labels in fstab

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-10-06 13:22 EDT by Gabriele Turchi
Modified:	2007-04-18 12:29 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-10-06 14:59:34 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gabriele Turchi 2000-10-06 13:22:49 EDT

I've configured a disk partition to be mounted on /var/spool/squid, and
fstab failed to mount them. Label too long? Also, using labels on a
"complex" system (I use a test system with more than 5 different root
partitions) sounds not so good to me... Is possible to disable that
feature?

Thanks,
	Gabriele Turchi

[P.S.: I'm sorry, my english is in alpha version.]

Comment 1 Michael Fulbright 2000-10-06 14:27:01 EDT

You can reset the labels on the partitions using the e2label command.

We check to make sure that no two partitions have the same label when creating
new filesystems.

Finally, Brent, could you try to reproduce the problem with mounting
/var/spool/squid?

Comment 2 Brent Fox 2000-10-06 14:59:19 EDT

I was unable to verify.  /var/spool/squid mounted on reboot after installation
with no problems.  I believe that this used to be a bug that now seems to be
fixed on our latest internal builds.  I'm closing the bug.  Please reopen if the
problem reappears

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