Bug 561 - missing functionality in tunefs
Summary: missing functionality in tunefs
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1995-06-25 07:50 UTC by Peter Wemm
Modified: 1995-06-25 07:50 UTC (History)
0 users

See Also:


Attachments
file.diff (2.63 KB, patch)
1995-06-25 07:50 UTC, Peter Wemm
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Wemm 1995-06-25 07:50:02 UTC
When tuneing filesystems with tunefs, it is not obvious what the current
parameters are.  You can use dumpfs, but that's not obvious which settings
are tuneable, and is far from clear to the non-guru (it's like using a 
hexdump of a tar archive to get a table-of-contents).

There is also an undocumented option in the man page that can be dangerous.
Suppose your disk driver decides to scramble all writes while you tell
tunefs to update all backup superblocks.

This suggested change adds a '-p' (print) switch to bring it in
line with some SVR4 systems.

# tunefs -p /dev/rsd0h
tunefs: maximum contiguous block count: (-a)               1
tunefs: rotational delay between contiguous blocks: (-d)   4 ms
tunefs: maximum blocks per file in a cylinder group: (-e)  1024
tunefs: minimum percentage of free space: (-m)             10%
tunefs: optimization preference: (-o)                      time

Fix: Apply this patch to tunefs.c and tunefs.8
How-To-Repeat: 
Use tunefs and dumpfs.
Comment 1 Joerg Wunsch freebsd_committer freebsd_triage 1995-06-25 18:46:49 UTC
State Changed
From-To: open->closed

Suggested fix applied (with minor, mostly optics, changes by me).