Print this page
4833 Remove volrmmount
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1/rmformat.1.man.txt
+++ new/usr/src/man/man1/rmformat.1.man.txt
1 1 RMFORMAT(1) User Commands RMFORMAT(1)
2 2
3 3
4 4
5 5 NAME
6 6 rmformat - removable rewritable media format utility
7 7
8 8 SYNOPSIS
9 9 rmformat [-DeHUv] [-b label] [-c blockno]
10 10 [-Fquick | long | force ] [-s filename] [devname]
11 11
12 12
13 13 rmformat -V read | write devname
14 14
15 15
16 16 rmformat -l [devname]
17 17
18 18
19 19 DESCRIPTION
20 20 The rmformat utility is used to format, label, partition, and perform
21 21 other miscellaneous functions on removable, rewritable media that
22 22 include floppy drives, and the PCMCIA memory and ata cards. The
23 23 rmformat utility should also be used with all USB mass storage
24 24 devices, including USB hard drives. This utility can also be used for
25 25 the verification and surface analysis and for repair of the bad sectors
26 26 found during verification if the drive or the driver supports bad block
27 27 management.
28 28
29 29
30 30 After formatting, rmformat writes the label, which covers the full
31 31 capacity of the media as one slice on floppy and PCMCIA memory cards to
32 32 maintain compatibility with the behavior of fdformat. The partition
33 33 information can be changed with the help of other options provided by
34 34 rmformat.
35 35
36 36 OPTIONS
37 37 The following options are supported:
38 38
39 39 -b label
40 40
41 41 Labels the media with a SUNOS label. A SUNOS volume label name is
42 42 restricted to 8 characters. For media size greater than 1 TB, an
43 43 EFI label is created. For writing a DOS Volume label, the user
44 44 should use mkfs_pcfs(1M).
45 45
46 46
47 47 -c blockno
48 48
49 49 Corrects and repairs the given block. This correct and repair
50 50 option may not be applicable to all devices supported by rmformat,
51 51 as some devices may have a drive with bad block management
52 52 capability and others may have this option implemented in the
53 53 driver. If the drive or driver supports bad block management, a
54 54 best effort is made to rectify the bad block. If the bad block
55 55 still cannot be rectified, a message is displayed to indicate the
56 56 failure to repair. The block number can be provided in decimal,
57 57 octal, or hexadecimal format.
58 58
59 59 The normal floppy and PCMCIA memory and ata cards do not support
60 60 bad block management.
61 61
62 62
63 63 -D
64 64
65 65 Formats a 720KB (3.5 inch) double density diskette. This is the
66 66 default for double density type drives. This option is needed if
67 67 the drive is a high or extended-density type.
68 68
69 69
70 70 -e
71 71
72 72 Ejects the media upon completion. This feature may not be available
73 73 if the drive does not support motorized eject.
74 74
75 75
76 76 -F quick | long | force
77 77
78 78 Formats the media.
79 79
80 80 The quick option starts a format without certification or format
81 81 with limited certification of certain tracks on the media.
82 82
83 83 The long option starts a complete format. For some devices this
84 84 might include the certification of the whole media by the drive
85 85 itself.
86 86
87 87 The force option to format is provided to start a long format
88 88 without user confirmation before the format is started.
89 89
90 90 In legacy media such as floppy drives, all options start a long
91 91 format depending on the mode (Extended Density mode, High Density
92 92 mode, or Double Density mode) with which the floppy drive operates
93 93 by default. On PCMCIA memory cards, all options start a long
94 94 format.
95 95
96 96
97 97 -H
98 98
99 99 Formats a 1.44 MB (3.5 inch) high density diskette. This is the
100 100 default for high density type drives. It is needed if the drive is
101 101 the Extended Density type.
102 102
103 103
104 104 -l
105 105
106 106 Lists all removable devices. By default, without any options,
107 107 rmformat also lists all removable devices. If the dev_name is
108 108 given, rmformat lists the device associated with the dev_name. The
109 109 output shows the device pathname, vendor information, and the
110 110 device type.
111 111
112 112
113 113 -s filename
114 114
115 115 Enables the user to lay out the partition information in the SUNOS
116 116 label.
117 117
118 118 The user should provide a file as input with information about each
119 119 slice in a format providing byte offset, size required, tags, and
120 120 flags, as follows:
121 121
122 122 slices: n = offset, size [, flags, tags]
123 123
124 124
125 125 where n is the slice number, offset is the byte offset at which the
126 126 slice n starts, and size is the required size for slice n. Both
127 127 offset and size must be a multiple of 512 bytes. These numbers can
128 128 be represented as decimal, hexadecimal, or octal numbers. No
129 129 floating point numbers are accepted. Details about maximum number
130 130 of slices can be obtained from the System Administration Guide:
131 131 Basic Administration.
132 132
133 133 To specify the size or offset in kilobytes, megabytes, or
134 134 gigabytes, add KB, MB, GB, respectively. A number without a suffix
135 135 is assumed to be a byte offset. The flags are represented as
136 136 follows:
137 137
138 138 wm = read-write, mountable
139 139 wu = read-write, unmountable
140 140 ru = read-only, unmountable
141 141
142 142
143 143 The tags are represented as follows: unassigned, boot, root, swap,
144 144 usr, backup, stand, var, home, alternates.
145 145
146 146 The tags and flags can be omitted from the four tuple when finer
147 147 control on those values is not required. It is required to omit
148 148 both or include both. If the tags and flags are omitted from the
149 149 four tuple for a particular slice, a default value for each is
150 150 assumed. The default value for flags is wm and for tags is
151 151 unassigned.
152 152
153 153 Either full tag names can be provided or an abbreviation for the
154 154 tags can be used. The abbreviations can be the first two or more
155 155 letters from the standard tag names. rmformat is case insensitive
156 156 in handling the defined tags & flags.
157 157
158 158 Slice specifications are separated by :
159 159
160 160 For example:
161 161
162 162 slices: 0 = 0, 30MB, "wm", "home" :
163 163 1 = 30MB, 51MB :
164 164 2 = 0, 100MB, "wm", "backup" :
165 165 6 = 81MB, 19MB
166 166
167 167
168 168 rmformat does the necessary checking to detect any overlapping
169 169 partitions or illegal requests to addresses beyond the capacity of
170 170 the media under consideration. There can be only one slice
171 171 information entry for each slice n. If multiple slice information
172 172 entries for the same slice n are provided, an appropriate error
173 173 message is displayed. The slice 2 is the backup slice covering the
174 174 whole disk capacity. The pound sign character, #, can be used to
175 175 describe a line of comments in the input file. If the line starts
176 176 with #, then rmformat ignores all the characters following # until
177 177 the end of the line.
178 178
179 179 Partitioning some of the media with very small capacity is
180 180 permitted, but be cautious in using this option on such devices.
181 181
182 182
183 183 -U
184 184
185 185 Performs umount on any file systems and then formats. See
186 186 mount(1M). This option unmounts all the mounted slices and issues a
187 187 long format on the device requested.
188 188
189 189
190 190 -V read | write
191 191
192 192 Verifies each block of media after format. The write verification
193 193 is a destructive mechanism. The user is queried for confirmation
194 194 before the verification is started. The output of this option is a
195 195 list of block numbers, which are identified as bad.
196 196
197 197 The read verification only verifies the blocks and report the
198 198 blocks which are prone to errors.
199 199
200 200 The list of block numbers displayed can be used with the -c option
201 201 for repairing.
202 202
203 203
204 204 OPERANDS
205 205 The following operand is supported:
206 206
207 207 devname
208 208
209 209 devname can be provided as absolute device pathname or relative
210 210 pathname for the device from the current working directory or the
211 211 nickname, such as cdrom or rmdisk.
212 212
213 213 For floppy devices, to access the first drive use /dev/rdiskette0
214 214 (for systems without volume management) or floppy0 (for systems
215 215 with volume management). Specify /dev/rdiskette1 (for systems
216 216 without volume management) or floppy1 (for systems with volume
217 217 management) to use the second drive.
218 218
219 219 For systems without volume management running, the user can also
220 220 provide the absolute device pathname as /dev/rdsk/c?t?d?s? or the
221 221 appropriate relative device pathname from the current working
222 222 directory.
223 223
224 224
225 225 EXAMPLES
226 226 Example 1 Formatting a Diskette
227 227
228 228 example$ rmformat -F quick /dev/rdiskette
229 229 Formatting will erase all the data on disk.
230 230 Do you want to continue? (y/n)y
231 231
232 232
233 233
234 234 Example 2 Formatting a Diskette for a UFS File System
235 235
236 236
237 237 The following example formats a diskette and creates a UFS file system:
238 238
239 239
240 240 example$ rmformat -F quick /dev/aliases/floppy0
241 241 Formatting will erase all the data on disk.
242 242 Do you want to continue? (y/n)y
243 243 example$ su
244 244 # /usr/sbin/newfs /dev/aliases/floppy0
245 245 newfs: construct a new file system /dev/rdiskette: (y/n)? y
246 246 /dev/rdiskette: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors
247 247 1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 128 i/g)
248 248 super-block backups (for fsck -F ufs -o b=#) at:
249 249 32, 640, 1184, 1792, 2336,
250 250 #
251 251
252 252
253 253
254 254 Example 3 Formatting Removable Media for a PCFS File System
255 255
256 256
257 257 The following example shows how to create an alternate fdisk partition:
258 258
259 259
260 260 example$ rmformat -F quick /dev/rdsk/c0t4d0s2:c
261 261 Formatting will erase all the data on disk.
262 262 Do you want to continue? (y/n)y
263 263 example$ su
264 264 # fdisk /dev/rdsk/c0t4d0s2:c
265 265 # mkfs -F pcfs /dev/rdsk/c0t4d0s2:c
266 266 Construct a new FAT file system on /dev/rdsk/c0t4d0s2:c: (y/n)? y
267 267 #
268 268
269 269
270 270
271 271
272 272 The following example describes how to create a PCFS file system
273 273 without an fdisk partition:
274 274
275 275
276 276 example$ rmformat -F quick /dev/rdiskette
277 277 Formatting will erase all the data on disk.
278 278 Do you want to continue? (y/n)y
279 279 example$ su
280 280 # mkfs -F pcfs -o nofdisk,size=2 /dev/rdiskette
281 281 Construct a new FAT file system on /dev/rdiskette: (y/n)? y
282 282 #
283 283
284 284
285 285
286 286 Example 4 Listing All Removable Devices
287 287
288 288
289 289 The following example shows how to list removable devices. This output
290 290 shows a long listing of such devices.
291 291
292 292
293 293 example$ rmformat -l
294 294 Looking for devices...
295 295 Logical Node: /dev/rdsk/c5t0d0s2
296 296 Physical Node: /pci@1e,600000/usb@b/hub@2/storage@4/disk@0,0
297 297 Connected Device: TEAC FD-05PUB 1026
298 298 Device Type: Floppy drive
299 299 Bus: USB
300 300 Size: 1.4 MB
301 301 Label: floppy
302 302 Access permissions: Medium is not write protected.
303 303
304 304
305 305
306 306 FILES
307 307 /dev/diskette0
308 308
309 309 Directory providing block device access for the media in floppy
310 310 drive 0.
311 311
312 312
313 313 /dev/rdiskette0
314 314
315 315 Directory providing character device access for the media in floppy
316 316 drive 0.
317 317
318 318
319 319 /dev/aliases
320 320
321 321 Directory providing symbolic links to the character devices for the
322 322 different media under the control of volume management using
323 323 appropriate alias.
324 324
325 325
326 326 /dev/aliases/floppy0
327 327
328 328 Symbolic link to the character device for the media in floppy drive
329 329 0.
330 330
331 331
332 332 /dev/rdiskette
333 333
334 334 Symbolic link providing character device access for the media in
335 335 the primary floppy drive, usually drive 0.
336 336
337 337
338 338 /dev/dsk
339 339
340 340 Directory providing block device access for the PCMCIA memory and
341 341 ata cards and removable media devices.
342 342
343 343
344 344 /dev/rdsk
345 345
346 346 Directory providing character device access for the PCMCIA memory
347 347 and ata cards and removable media devices.
348 348
349 349
350 350 /dev/aliases/pcmemS
351 351
352 352 Symbolic link to the character device for the PCMCIA memory card in
353 353 socket S, where S represents a PCMCIA socket number.
354 354
355 355
356 356 /dev/aliases/rmdisk0
357 357
358 358 Symbolic link to the generic removable media device that is not a
359 359 CD-ROM, floppy, DVD-ROM, PCMCIA memory card, and so forth.
360 360
361 361
362 362 /dev/rdsk
363 363
364 364 Directory providing character device access for the PCMCIA memory
|
↓ open down ↓ |
364 lines elided |
↑ open up ↑ |
365 365 and ata cards and other removable devices.
366 366
367 367
368 368 /dev/dsk
369 369
370 370 Directory providing block device access for the PCMCIA memory and
371 371 ata cards and other removable media devices.
372 372
373 373
374 374 SEE ALSO
375 - cpio(1), eject(1), fdformat(1), tar(1), volcheck(1), volrmmount(1),
376 - format(1M), mkfs_pcfs(1M), mount(1M), newfs(1M), prtvtoc(1M),
377 - rmmount(1M), rpc.smserverd(1M), attributes(5), scsa2usb(7D), sd(7D),
378 - pcfs(7FS), udfs(7FS)
375 + cpio(1), eject(1), fdformat(1), tar(1), volcheck(1), format(1M),
376 + mkfs_pcfs(1M), mount(1M), newfs(1M), prtvtoc(1M), rmmount(1M),
377 + rpc.smserverd(1M), attributes(5), scsa2usb(7D), sd(7D), pcfs(7FS),
378 + udfs(7FS)
379 379
380 380
381 381 System Administration Guide: Basic Administration
382 382
383 383 NOTES
384 384 A rewritable media or PCMCIA memory card or PCMCIA ata card containing
385 385 a ufs file system created on a SPARC-based system (using newfs(1M)) is
386 386 not identical to a rewritable media or PCMCIA memory card containing a
387 387 ufs file system created on an x86 based system. Do not interchange any
388 388 removable media containing ufs between these platforms; use cpio(1) or
389 389 tar(1) to transfer files on diskettes or memory cards between them. For
390 390 interchangeable filesystems refer to pcfs(7FS) and udfs(7FS).
391 391
392 392
|
↓ open down ↓ |
4 lines elided |
↑ open up ↑ |
393 393 rmformat might not list all removable devices in virtualization
394 394 environments.
395 395
396 396 BUGS
397 397 Currently, bad sector mapping is not supported on floppy diskettes or
398 398 PCMCIA memory cards. Therefore, a diskette or memory card is unusable
399 399 if rmformat finds an error (bad sector).
400 400
401 401
402 402
403 - February 19, 2009 RMFORMAT(1)
403 + May 2, 2014 RMFORMAT(1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX