Bug 1053138

Summary: Inconsistancy regarding labeling between dosfslabel and mkfs.fat and documentation
Product: [Fedora] Fedora Reporter: mulhern <amulhern>
Component: dosfstoolsAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jskarvad
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:27:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mulhern 2014-01-14 18:11:41 UTC
Description of problem:

1) Not setting label via mkfs.fat and reading label w/dosfslabel yields string "NO NAME" but documentation says default is no label. So, either documentation
is wrong or dosfslabel prefers returning "NO NAME" to returning an empty string,
which is wrong, because "NO NAME" may be legitimate label and
it is not the same as no label.
2) If I set label to "start" via mkfs.fat and I read the label via dosfslabel the result is "START", i.e., capitalized. But, if I set the label via dosfslabel to "an fs", and I read the label via dosfslabel the result is "an fs", i.e., not capitalized.

Version-Release number of selected component (if applicable):

Installed w/ yum, so here's the yum info.

[root@localhost blivet]# yum info dosfstoolsLoaded plugins: langpacks, refresh-packagekit
Installed Packages
Name        : dosfstools
Arch        : x86_64
Version     : 3.0.22
Release     : 3.fc19
Size        : 243 k
Repo        : installed
From repo   : updates
Summary     : Utilities for making and checking MS-DOS FAT filesystems on Linux
URL         : http://www.daniel-baumann.ch/software/dosfstools/
License     : GPLv3+
Description : The dosfstools package includes the mkdosfs and dosfsck utilities,
            : which respectively make and check MS-DOS FAT filesystems on hard
            : drives or on floppies.

How reproducible:

Consistantly.

Steps to Reproduce:

Description of problem should be enough.

Actual results:

Inconsistancy wrt. labeling among the dosfstools

Expected results:

Consistancy wrt. labeling among the dosfstools

Additional info:

None

Comment 1 Fedora End Of Life 2015-05-29 10:29:59 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 2 Fedora End Of Life 2015-06-29 14:27:06 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.