summaryrefslogtreecommitdiffstats
path: root/sys-utils/mount.8
blob: d5fa55f43b68ce636e114315370ed38f7ca6cf40 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
.\" Copyright (c) 1996-2004 Andries Brouwer
.\" Copyright (C) 2006-2012 Karel Zak <kzak@redhat.com>
.\"
.\" This page is somewhat derived from a page that was
.\" (c) 1980, 1989, 1991 The Regents of the University of California
.\" and had been heavily modified by Rik Faith and myself.
.\" (Probably no BSD text remains.)
.\" Fragments of text were written by Werner Almesberger, Remy Card,
.\" Stephen Tweedie and Eric Youngdale.
.\"
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public License along
.\" with this program; if not, write to the Free Software Foundation, Inc.,
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
.\"
.TH MOUNT 8 "August 2015" "util-linux" "System Administration"
.SH NAME
mount \- mount a filesystem
.SH SYNOPSIS
.B mount
.RB [ \-h | \-V ]
.LP
.B mount
.RB [ \-l ]
.RB [ \-t
.IR fstype ]
.LP
.B mount \-a
.RB [ \-fFnrsvw ]
.RB [ \-t
.IR fstype ]
.RB [ \-O
.IR optlist ]
.LP
.B mount
.RB [ \-fnrsvw ]
.RB [ \-o
.IR options ]
.IR device | mountpoint
.LP
.B mount
.RB [ \-fnrsvw ]
.RB [ \-t
.IB fstype ]
.RB [ \-o
.IR options ]
.I device mountpoint
.LP
.B mount
.BR \-\-bind | \-\-rbind | \-\-move
.I olddir newdir
.LP
.B mount
.BR \-\-make\- { shared | slave | private | unbindable | rshared | \
rslave | rprivate | runbindable }
.I mountpoint
.SH DESCRIPTION
All files accessible in a Unix system are arranged in one big
tree, the file hierarchy, rooted at
.IR / .
These files can be spread out over several devices.  The
.B mount
command serves to attach the filesystem found on some device
to the big file tree.  Conversely, the
.BR umount (8)
command will detach it again.  The filesystem is used to control how data is
stored on the device or provided in a virtual way by network or other services.

The standard form of the
.B mount
command is:
.RS

.BI "mount \-t" " type device dir"

.RE
This tells the kernel to attach the filesystem found on
.I device
(which is of type
.IR type )
at the directory
.IR dir .
The option \fB\-t \fItype\fR is optional.  The
.B mount
command is usually able to detect a filesystem.  The root permissions are necessary
to mount a filesystem by default.  See section "Non-superuser mounts" below for more details.
The previous contents (if any) and owner and mode of
.I dir
become invisible, and as long as this filesystem remains mounted,
the pathname
.I dir
refers to the root of the filesystem on
.IR device .

If only the directory or the device is given, for example:
.RS
.sp
.B mount /dir
.sp
.RE
then \fBmount\fR looks for a mountpoint (and if not found then for a device) in the
.I /etc/fstab
file.  It's possible to use the
.B \-\-target
or
.B \-\-source
options to avoid ambiguous interpretation of the given argument.
For example:
.RS
.sp
.B mount \-\-target /mountpoint
.sp
.RE

The same filesystem may be mounted more than once, and in some cases (e.g.,
network filesystems) the same filesystem may be mounted on the same
mountpoint multiple times. The
.B mount
command does not implement any policy to
control this behavior. All behavior is controlled by the kernel and it is usually
specific to the filesystem driver. The exception is \fB\-\-all\fR, in this case
already mounted filesystems are ignored (see \fB\-\-all\fR below for more details).

.SS Listing the mounts
The listing mode is maintained for backward compatibility only.

For more robust and customizable output use
.BR findmnt (8),
\fBespecially in your scripts\fP.  Note that control characters in the
mountpoint name are replaced with '?'.

The following command lists all mounted filesystems (of type
.IR type ):
.RS
.sp
.BR "mount " [ \-l "] [" "\-t \fItype\/\fP" ]
.sp
.RE
The option \fB\-l\fR adds labels to this listing.  See below.

.SS Indicating the device and filesystem
Most devices are indicated by a filename (of a block special device), like
.IR /dev/sda1 ,
but there are other possibilities.  For example, in the case of an NFS mount,
.I device
may look like
.IR knuth.cwi.nl:/dir .
.PP
The device names of disk partitions are unstable; hardware reconfiguration,
and adding or removing a device can cause changes in names.
This is the reason why it's
strongly recommended to use filesystem or partition identifiers like UUID or
LABEL. Currently supported identifiers (tags):
.RS
.TP
LABEL=\fIlabel\fR
Human readable filesystem identifier. See also \fB\-L\fR.
.TP
UUID=\fIuuid\fR
Filesystem universally unique identifier. The format of the UUID is usually a
series of hex digits separated by hyphens. See also \fB\-U\fR.
.sp
Note that
.BR mount (8)
uses UUIDs as strings.  The UUIDs from the command line or from
.BR fstab (5)
are not converted to internal binary representation.  The string representation
of the UUID should be based on lower case characters.
.TP
PARTLABEL=\fIlabel\fR
Human readable partition identifier.  This identifier is independent on
filesystem and does not change by mkfs or mkswap operations It's supported
for example for GUID Partition Tables (GPT).
.TP
PARTUUID=\fIuuid\fR
Partition universally unique identifier.  This identifier is independent on
filesystem and does not change by mkfs or mkswap operations  It's supported
for example for GUID Partition Tables (GPT).
.TP
ID=\fIid\fR
Hardware block device ID as generated by udevd.  This identifier is usually
based on WWN (unique storage identifier) and assigned by the hardware
manufacturer.  See \fBls /dev/disk/by-id\fR for more details, this directory
and running udevd is required.  This identifier is not recommended for generic
use as the identifier is not strictly defined and it depends on udev, udev rules
and hardware.
.RE
.sp
The command \fBlsblk \-\-fs\fR provides an overview of filesystems, LABELs and UUIDs
on available block devices.  The command \fBblkid \-p <device>\fR provides details about
a filesystem on the specified device.

Don't forget that there is no guarantee that UUIDs and labels are really
unique, especially if you move, share or copy the device.  Use
.B "lsblk \-o +UUID,PARTUUID"
to verify that the UUIDs are really unique in your system.

The recommended setup is to use tags (e.g.\& \fBUUID=\fIuuid\fR) rather than
.I /dev/disk/by-{label,uuid,id,partuuid,partlabel}
udev symlinks in the
.I /etc/fstab
file.  Tags are
more readable, robust and portable.  The
.BR mount (8)
command internally uses udev
symlinks, so the use of symlinks in
.I /etc/fstab
has no advantage over tags.
For more details see
.BR libblkid (3).

The
.I proc
filesystem is not associated with a special device, and when
mounting it, an arbitrary keyword\(emfor example,
.IR proc \(emcan
be used instead of a device specification.
(The customary choice
.I none
is less fortunate: the error message `none already mounted' from
.B mount
can be confusing.)

.SS The files /etc/fstab, /etc/mtab and /proc/mounts
The file
.I /etc/fstab
(see
.BR fstab (5)),
may contain lines describing what devices are usually
mounted where, using which options.  The default location of the
.BR fstab (5)
file can be overridden with the
.BI \-\-fstab " path"
command-line option (see below for more details).
.LP
The command
.RS
.sp
.B mount \-a
.RB [ \-t
.IR type ]
.RB [ \-O
.IR optlist ]
.sp
.RE
(usually given in a bootscript) causes all filesystems mentioned in
.I fstab
(of the proper type and/or having or not having the proper options)
to be mounted as indicated, except for those whose line contains the
.B noauto
keyword.  Adding the
.B \-F
option will make \fBmount\fR fork, so that the
filesystems are mounted in parallel.
.LP
When mounting a filesystem mentioned in
.I fstab
or
.IR mtab ,
it suffices to specify on the command line only the device, or only the mount point.
.sp
The programs
.B mount
and
.B umount
traditionally maintained a list of currently mounted filesystems in the file
.IR /etc/mtab .
The support for regular classic
.I /etc/mtab
is completely disabled at compile time by default, because on current Linux
systems it is better to make
.I /etc/mtab
a symlink to
.I /proc/mounts
instead. The regular
.I mtab
file maintained in userspace cannot reliably
work with namespaces, containers and other advanced Linux features.
If the regular
.I mtab
support is enabled, then it's possible to
use the file as well as the symlink.
.sp
If no arguments are given to
.BR mount ,
the list of mounted filesystems is printed.
.sp
If you want to override mount options from
.IR /etc/fstab ,
you have to use the \fB\-o\fR option:
.RS
.sp
.BI mount " device" \fR| "dir " \-o " options"
.sp
.RE
and then the mount options from the command line will be appended to
the list of options from
.IR /etc/fstab .
This default behaviour can be changed using the
\fB\-\-options\-mode\fR
command-line option.
The usual behavior is that the last option wins if there are conflicting
ones.
.sp
The
.B mount
program does not read the
.I /etc/fstab
file if both
.I device
(or LABEL, UUID, ID, PARTUUID or PARTLABEL) and
.I dir
are specified.  For example, to mount device
.BR foo " at " /dir :
.RS
.sp
.B "mount /dev/foo /dir"
.sp
.RE
This default behaviour can be changed by using the
\fB\-\-options\-source\-force\fR command-line option
to always read configuration from
.IR fstab .
For non-root users
.B mount
always reads the
.I fstab
configuration.

.SS Non-superuser mounts
Normally, only the superuser can mount filesystems.
However, when
.I fstab
contains the
.B user
option on a line, anybody can mount the corresponding filesystem.
.LP
Thus, given a line
.RS
.sp
.B "/dev/cdrom  /cd  iso9660  ro,user,noauto,unhide"
.sp
.RE
any user can mount the iso9660 filesystem found on an inserted CDROM
using the command:
.PP
.RS
.B "mount /cd"
.sp
.RE
Note that \fBmount\fR is very strict about non-root users and all paths
specified on command line are verified before
.I fstab
is parsed or a helper
program is executed. It's strongly recommended to use a valid mountpoint to
specify filesystem, otherwise \fBmount\fR may fail. For example it's a bad idea
to use NFS or CIFS source on command line.
.PP
Since util-linux 2.35, \fBmount\fR does not exit when user permissions are
inadequate according to libmount's internal security rules.
Instead, it drops suid permissions
and continues as regular non-root user. This behavior supports use-cases where
root permissions are not necessary (e.g., fuse filesystems, user namespaces,
etc).
.PP
For more details, see
.BR fstab (5).
Only the user that mounted a filesystem can unmount it again.
If any user should be able to unmount it, then use
.B users
instead of
.B user
in the
.I fstab
line.
The
.B owner
option is similar to the
.B user
option, with the restriction that the user must be the owner
of the special file.  This may be useful e.g.\& for
.I /dev/fd
if a login script makes the console user owner of this device.
The
.B group
option is similar, with the restriction that the user must be a
member of the group of the special file.

.SS Bind mount operation
Remount part of the file hierarchy somewhere else.  The call is:

.RS
.br
.B mount \-\-bind
.I olddir newdir
.RE

or by using this
.I fstab
entry:

.RS
.br
.BI / olddir
.BI / newdir
.B none bind
.RE

After this call the same contents are accessible in two places.

It is important to understand that "bind" does not create any second-class
or special node in the kernel VFS. The "bind" is just another operation to
attach a filesystem. There is nowhere stored information that the filesystem
has been attached by a "bind" operation. The \fIolddir\fR and \fInewdir\fR are
independent and the \fIolddir\fR may be unmounted.

One can also remount a single file (on a single file).  It's also
possible to use a bind mount to create a mountpoint from a regular
directory, for example:

.RS
.br
.B mount \-\-bind foo foo
.RE

The bind mount call attaches only (part of) a single filesystem, not possible
submounts.  The entire file hierarchy including submounts can be attached
a second place by using:

.RS
.br
.B mount \-\-rbind
.I olddir newdir
.RE

Note that the filesystem mount options maintained by the kernel will remain the same as those
on the original mount point.  The userspace mount options (e.g., _netdev) will not be copied
by
.B mount
and it's necessary to explicitly specify the options on the
.B mount
command line.

Since util-linux 2.27
.BR mount (8)
permits changing the mount options by passing the
relevant options along with
.BR \-\-bind .
For example:

.RS
.br
.B mount \-o bind,ro foo foo
.RE

This feature is not supported by the Linux kernel; it is implemented in userspace
by an additional \fBmount\fR(2) remounting system call.
This solution is not atomic.

The alternative (classic) way to create a read-only bind mount is to use the remount
operation, for example:

.RS
.br
.B mount \-\-bind
.I olddir newdir
.br
.B mount \-o remount,bind,ro
.I olddir newdir
.RE

Note that a read-only bind will create a read-only mountpoint (VFS entry),
but the original filesystem superblock will still be writable, meaning that the
.I olddir
will be writable, but the
.I newdir
will be read-only.

It's also possible to change nosuid, nodev, noexec, noatime, nodiratime and
relatime VFS entry flags via a "remount,bind" operation.
The other flags (for example
filesystem-specific flags) are silently ignored.  It's impossible to change mount
options recursively (for example with \fB\-o rbind,ro\fR).

Since util-linux 2.31,
.B mount
ignores the \fBbind\fR flag from
.I /etc/fstab
on a
.B remount
operation
(if "\-o remount" is specified on command line).
This is necessary to fully control
mount options on remount by command line. In previous versions the bind
flag has been always applied and it was impossible to re-define mount options
without interaction with the bind semantic. This
.BR mount (8)
behavior does not affect situations when "remount,bind" is specified in the
.I /etc/fstab
file.

.SS The move operation
Move a
.B mounted tree
to another place (atomically).  The call is:

.RS
.br
.B mount \-\-move
.I olddir newdir
.RE

This will cause the contents which previously appeared under
.I olddir
to now be accessible under
.IR newdir .
The physical location of the files is not changed.
Note that
.I olddir
has to be a mountpoint.

Note also that moving a mount residing under a shared mount is invalid and
unsupported.  Use
.B findmnt \-o TARGET,PROPAGATION
to see the current propagation flags.

.SS Shared subtree operations
Since Linux 2.6.15 it is possible to mark a mount and its submounts as shared,
private, slave or unbindable.  A shared mount provides the ability to create mirrors
of that mount such that mounts and unmounts within any of the mirrors propagate
to the other mirror.  A slave mount receives propagation from its master, but
not vice versa.  A private mount carries no propagation abilities.  An
unbindable mount is a private mount which cannot be cloned through a bind
operation.  The detailed semantics are documented in
.I Documentation/filesystems/sharedsubtree.txt
file in the kernel source tree; see also
.BR mount_namespaces (7).

Supported operations are:

.RS
.nf
.BI "mount \-\-make\-shared " mountpoint
.BI "mount \-\-make\-slave " mountpoint
.BI "mount \-\-make\-private " mountpoint
.BI "mount \-\-make\-unbindable " mountpoint
.fi
.RE

The following commands allow one to recursively change the type of all the
mounts under a given mountpoint.

.RS
.nf
.BI "mount \-\-make\-rshared " mountpoint
.BI "mount \-\-make\-rslave " mountpoint
.BI "mount \-\-make\-rprivate " mountpoint
.BI "mount \-\-make\-runbindable " mountpoint
.fi
.RE

.BR mount (8)
.B does not read
.BR fstab (5)
when a \fB\-\-make-\fR* operation is requested.  All necessary information has to be
specified on the command line.

Note that the Linux kernel does not allow changing multiple propagation flags
with a single
.BR mount (2)
system call, and the flags cannot be mixed with other mount options and operations.

Since util-linux 2.23 the \fBmount\fR command can be used to do more propagation
(topology) changes by one mount(8) call and do it also together with other
mount operations.  This feature is EXPERIMENTAL.  The propagation flags are applied
by additional \fBmount\fR(2) system calls when the preceding mount operations
were successful.  Note that this use case is not atomic.  It is possible to
specify the propagation flags in
.BR fstab (5)
as mount options
.RB ( private ,
.BR slave ,
.BR shared ,
.BR unbindable ,
.BR rprivate ,
.BR rslave ,
.BR rshared ,
.BR runbindable ).

For example:

.RS
.nf
.B mount \-\-make\-private \-\-make\-unbindable /dev/sda1 /foo
.fi
.RE

is the same as:

.RS
.nf
.B mount /dev/sda1 /foo
.B mount \-\-make\-private /foo
.B mount \-\-make\-unbindable /foo
.fi
.RE

.SH COMMAND-LINE OPTIONS
The full set of mount options used by an invocation of
.B mount
is determined by first extracting the
mount options for the filesystem from the
.I fstab
table, then applying any options specified by the
.B \-o
argument, and finally applying a
.BR \-r " or " \-w
option, when present.

The \fBmount\fR command does not pass all command-line options to the
\fB/sbin/mount.\fIsuffix\fR mount helpers.  The interface between \fBmount\fR
and the mount helpers is described below in the section \fBEXTERNAL HELPERS\fR.
.sp
Command-line options available for the
.B mount
command are:
.TP
.BR \-a , " \-\-all"
Mount all filesystems (of the given types) mentioned in
.I fstab
(except for those whose line contains the
.B noauto
keyword).  The filesystems are mounted following their order in
.IR fstab .
The
.B mount
command compares filesystem source, target (and fs root for bind
mount or btrfs) to detect already mounted filesystems. The kernel table with
already mounted filesystems is cached during \fBmount \-\-all\fR. This means
that all duplicated
.I fstab
entries will be mounted.
.sp
The option \fB\-\-all\fR is possible to use for remount operation too. In this
case all filters (\fB\-t\fR and \fB\-O\fR) are applied to the table of already
mounted filesystems.
.sp
Since version 2.35 is possible to use the command line option \fB\-o\fR to
alter mount options from
.I fstab
(see also \fB\-\-options\-mode\fR).
.sp
Note that it is a bad practice to use \fBmount \-a\fR for
.I fstab
checking. The recommended solution is \fBfindmnt \-\-verify\fR.
.TP
.BR \-B , " \-\-bind"
Remount a subtree somewhere else (so that its contents are available
in both places).  See above, under \fBBind mounts\fR.
.TP
.BR \-c , " \-\-no\-canonicalize"
Don't canonicalize paths.  The
.B mount
command canonicalizes all paths
(from the command line or
.IR fstab )
by default.  This option can be used
together with the
.B \-f
flag for already canonicalized absolute paths.  The option is designed for mount
helpers which call \fBmount \-i\fR.  It is strongly recommended to not use this
command-line option for normal mount operations.
.sp
Note that \fBmount\fR(8) does not pass this option to the
\fB/sbin/mount.\fItype\fR helpers.
.TP
.BR \-F , " \-\-fork"
(Used in conjunction with
.BR \-a .)
Fork off a new incarnation of \fBmount\fR for each device.
This will do the mounts on different devices or different NFS servers
in parallel.
This has the advantage that it is faster; also NFS timeouts proceed in
parallel.
A disadvantage is that the order of the mount operations is undefined.
Thus, you cannot use this option if you want to mount both
.I /usr
and
.IR /usr/spool .
.IP "\fB\-f, \-\-fake\fP"
Causes everything to be done except for the actual system call; if it's not
obvious, this ``fakes'' mounting the filesystem.  This option is useful in
conjunction with the
.B \-v
flag to determine what the
.B mount
command is trying to do.  It can also be used to add entries for devices
that were mounted earlier with the \fB\-n\fR option.  The \fB\-f\fR option
checks for an existing record in
.I /etc/mtab
and fails when the record already
exists (with a regular non-fake mount, this check is done by the kernel).
.IP "\fB\-i, \-\-internal\-only\fP"
Don't call the \fB/sbin/mount.\fIfilesystem\fR helper even if it exists.
.TP
.BR \-L , " \-\-label " \fIlabel
Mount the partition that has the specified
.IR label .
.TP
.BR \-l , " \-\-show\-labels"
Add the labels in the mount output.  \fBmount\fR must have
permission to read the disk device (e.g.\& be set-user-ID root) for this to work.
One can set such a label for ext2, ext3 or ext4 using the
.BR e2label (8)
utility, or for XFS using
.BR xfs_admin (8),
or for reiserfs using
.BR reiserfstune (8).
.TP
.BR \-M , " \-\-move"
Move a subtree to some other place.  See above, the subsection
\fBThe move operation\fR.
.TP
.BR \-n , " \-\-no\-mtab"
Mount without writing in
.IR /etc/mtab .
This is necessary for example when
.I /etc
is on a read-only filesystem.
.TP
.BR \-N , " \-\-namespace " \fIns
Perform the mount operation in the mount namespace specified by \fIns\fR.
\fIns\fR is either PID of process running in that namespace
or special file representing that namespace.
.sp
.BR mount (8)
switches to the mount namespace when it reads
.IR /etc/fstab ,
writes
.I /etc/mtab
(or writes to
.IR /run/mount )
and calls the
.BR mount (2)
system call, otherwise it runs in the original mount namespace.
This means that the target namespace does not have
to contain any libraries or other requirements necessary to execute the
.BR mount (2)
call.
.sp
See \fBmount_namespaces\fR(7) for more information.
.TP
.BR \-O , " \-\-test\-opts " \fIopts
Limit the set of filesystems to which the
.B \-a
option applies.  In this regard it is like the
.B \-t
option except that
.B \-O
is useless without
.BR \-a .
For example, the command:
.RS
.RS
.sp
.B "mount \-a \-O no_netdev"
.sp
.RE
mounts all filesystems except those which have the option
.I _netdev
specified in the options field in the
.I /etc/fstab
file.

It is different from
.B \-t
in that each option is matched exactly; a leading
.B no
at the beginning of one option does not negate the rest.

The
.B \-t
and
.B \-O
options are cumulative in effect; that is, the command
.RS
.sp
.B "mount \-a \-t ext2 \-O _netdev"
.sp
.RE
mounts all ext2 filesystems with the _netdev option, not all filesystems
that are either ext2 or have the _netdev option specified.
.RE
.TP
.BR \-o , " \-\-options " \fIopts
Use the specified mount options.  The \fIopts\fR argument is
a comma-separated list.  For example:
.RS
.RS
.sp
.B "mount LABEL=mydisk \-o noatime,nodev,nosuid"
.sp
.RE

For more details, see the
.B FILESYSTEM-INDEPENDENT MOUNT OPTIONS
and
.B FILESYSTEM-SPECIFIC MOUNT OPTIONS
sections.
.RE

.TP
.BR "\-\-options\-mode " \fImode
Controls how to combine options from
.IR fstab / mtab
with options from the command line.
\fImode\fR can be one of
.BR ignore ", " append ", " prepend " or " replace .
For example, \fBappend\fR means that options from
.I fstab
are appended to options from the command line.
The default value is \fBprepend\fR -- it means command line options are evaluated after
.I fstab
options.
Note that the last option wins if there are conflicting ones.

.TP
.BR "\-\-options\-source " \fIsource
Source of default options.
\fIsource\fR is a comma-separated list of
.BR fstab ", " mtab " and " disable .
\fBdisable\fR disables
.BR fstab " and " mtab
and disables \fB\-\-options\-source\-force\fR.
The default value is \fBfstab,mtab\fR.

.TP
.B \-\-options\-source\-force
Use options from
.IR fstab / mtab
even if both \fIdevice\fR and \fIdir\fR are specified.

.TP
.BR \-R , " \-\-rbind"
Remount a subtree and all possible submounts somewhere else (so that its
contents are available in both places).  See above, the subsection
\fBBind mounts\fR.
.TP
.BR \-r , " \-\-read\-only"
Mount the filesystem read-only.  A synonym is
.BR "\-o ro" .
.sp
Note that, depending on the filesystem type, state and kernel behavior, the
system may still write to the device.  For example, ext3 and ext4 will replay the
journal if the filesystem is dirty.  To prevent this kind of write access, you
may want to mount an ext3 or ext4 filesystem with the \fBro,noload\fR mount
options or set the block device itself to read-only mode, see the
.BR blockdev (8)
command.
.TP
.B \-s
Tolerate sloppy mount options rather than failing.  This will ignore mount
options not supported by a filesystem type.  Not all filesystems support this
option.  Currently it's supported by the \fBmount.nfs\fR mount helper only.
.TP
.BI \-\-source " device"
If only one argument for the mount command is given, then the argument might be
interpreted as the target (mountpoint) or source (device).
This option allows you to
explicitly define that the argument is the mount source.
.TP
.BI \-\-target " directory"
If only one argument for the mount command is given, then the argument might be
interpreted as the target (mountpoint) or source (device).
This option allows you to
explicitly define that the argument is the mount target.
.TP
.BI \-\-target\-prefix " directory"
Prepend the specified directory to all mount targets.
This option can be used to follow
.IR fstab ,
but mount operations are done in another place, for example:
.RS
.RS
.sp
.B "mount \-\-all \-\-target\-prefix /chroot \-o X\-mount.mkdir"
.sp
.RE
mounts all from system
.I fstab
to
.IR /chroot ,
all missing mountpoint are created
(due to X-mount.mkdir).  See also \fB\-\-fstab\fP to use an alternative
.IR fstab .
.RE
.TP
.BR \-T , " \-\-fstab " \fIpath
Specifies an alternative
.I fstab
file.
If \fIpath\fP is a directory, then the files
in the directory are sorted by
.BR strverscmp (3);
files that start with "."\& or without an
.I \&.fstab
extension are ignored.  The option
can be specified more than once.  This option is mostly designed for initramfs
or chroot scripts where additional configuration is specified beyond standard
system configuration.
.sp
Note that \fBmount\fR(8) does not pass the option \fB\-\-fstab\fP to the
\fB/sbin/mount.\fItype\fR helpers, meaning that the alternative
.I fstab
files will be
invisible for the helpers.  This is no problem for normal mounts, but user
(non-root) mounts always require
.I fstab
to verify the user's rights.
.TP
.BR \-t , " \-\-types " \fIfstype
The argument following the
.B \-t
is used to indicate the filesystem type.  The filesystem types which are
currently supported depend on the running kernel.  See
.I /proc/filesystems
and
.I /lib/modules/$(uname \-r)/kernel/fs
for a complete list of the filesystems.  The most common are ext2, ext3, ext4,
xfs, btrfs, vfat, sysfs, proc, nfs and cifs.
.sp
The programs
.B mount
and
.B umount
support filesystem subtypes.  The subtype is defined by a '.subtype' suffix.  For
example  'fuse.sshfs'.  It's recommended to use subtype notation rather than add
any prefix to the mount source (for example 'sshfs#example.com' is
deprecated).

If no
.B \-t
option is given, or if the
.B auto
type is specified,
.B mount
will try to guess the desired type.
Mount uses the blkid library for guessing the filesystem
type; if that does not turn up anything that looks familiar,
.B mount
will try to read the file
.IR /etc/filesystems ,
or, if that does not exist,
.IR /proc/filesystems .
All of the filesystem types listed there will be tried,
except for those that are labeled "nodev" (e.g.\&
.IR devpts ,
.I proc
and
.IR nfs ).
If
.I /etc/filesystems
ends in a line with a single *, mount will read
.I /proc/filesystems
afterwards.  While trying, all filesystem types will be
mounted with the mount option \fBsilent\fR.
.sp
The
.B auto
type may be useful for user-mounted floppies.
Creating a file
.I /etc/filesystems
can be useful to change the probe order (e.g., to try vfat before msdos
or ext3 before ext2) or if you use a kernel module autoloader.
.sp
More than one type may be specified in a comma-separated
list, for the
.B \-t
option as well as in an
.I /etc/fstab
entry.  The list of filesystem types for the
.B \-t
option can be prefixed with
.B no
to specify the filesystem types on which no action should be taken.
The prefix
.B no
has no effect when specified in an
.I /etc/fstab
entry.
.sp
The prefix
.B no
can be meaningful with the
.B \-a
option.  For example, the command
.RS
.RS
.sp
.B "mount \-a \-t nomsdos,smbfs"
.sp
.RE
mounts all filesystems except those of type
.I msdos
and
.IR smbfs .
.sp
For most types all the
.B mount
program has to do is issue a simple
.BR mount (2)
system call, and no detailed knowledge of the filesystem type is required.
For a few types however (like nfs, nfs4, cifs, smbfs, ncpfs) an ad hoc code is
necessary.  The nfs, nfs4, cifs, smbfs, and ncpfs filesystems
have a separate mount program.  In order to make it possible to
treat all types in a uniform way, \fBmount\fR will execute the program
.BI /sbin/mount. type
(if that exists) when called with type
.IR type .
Since different versions of the
.B smbmount
program have different calling conventions,
.B /sbin/mount.smbfs
may have to be a shell script that sets up the desired call.
.RE
.TP
.BR \-U , " \-\-uuid " \fIuuid
Mount the partition that has the specified
.IR uuid .
.TP
.BR \-v , " \-\-verbose"
Verbose mode.
.TP
.BR \-w , " \-\-rw" , " \-\-read\-write"
Mount the filesystem read/write.  Read-write is the kernel default and the
.B mount
default is to try read-only if the previous mount syscall with read-write flags
on write-protected devices of filesystems failed.
.sp
A synonym is
.BR "\-o rw" .

Note that specifying \fB\-w\fR on the command line forces \fBmount\fR to never
try read-only mount on write-protected devices or already mounted read-only
filesystems.
.TP
.BR \-V , " \-\-version"
Display version information and exit.
.TP
.BR \-h , " \-\-help"
Display help text and exit.

.SH FILESYSTEM-INDEPENDENT MOUNT OPTIONS
Some of these options are only useful when they appear in the
.I /etc/fstab
file.

Some of these options could be enabled or disabled by default
in the system kernel.  To check the current setting see the options
in
.IR /proc/mounts .
Note that filesystems also have per-filesystem
specific default mount options (see for example \fBtune2fs \-l\fP
output for extN filesystems).

The following options apply to any filesystem that is being
mounted (but not every filesystem actually honors them \(en e.g.\&, the
.B sync
option today has an effect only for ext2, ext3, ext4, fat, vfat, ufs and xfs):

.TP
.B async
All I/O to the filesystem should be done asynchronously.  (See also the
.B sync
option.)
.TP
.B atime
Do not use the \fBnoatime\fR feature, so the inode access time is controlled
by kernel defaults.  See also the descriptions of the \fB\%relatime\fR and
.B strictatime
mount options.
.TP
.B noatime
Do not update inode access times on this filesystem (e.g.\& for faster
access on the news spool to speed up news servers).  This works for all
inode types (directories too), so it implies \fB\%nodiratime\fR.
.TP
.B auto
Can be mounted with the
.B \-a
option.
.TP
.B noauto
Can only be mounted explicitly (i.e., the
.B \-a
option will not cause the filesystem to be mounted).
.TP
.na
.BR context=\fIcontext ", " fscontext=\fIcontext ", " defcontext=\fIcontext ", and " \%rootcontext=\fIcontext
.ad
The
.B context=
option is useful when mounting filesystems that do not support
extended attributes, such as a floppy or hard disk formatted with VFAT, or
systems that are not normally running under SELinux, such as an ext3 or ext4 formatted
disk from a non-SELinux workstation.  You can also use
.B context=
on filesystems you do not trust, such as a floppy.  It also helps in compatibility with
xattr-supporting filesystems on earlier 2.4.<x> kernel versions.  Even where
xattrs are supported, you can save time not having to label every file by
assigning the entire disk one security context.

A commonly used option for removable media is
.BR \%context="system_u:object_r:removable_t" .

Two other options are
.B fscontext=
and
.BR defcontext= ,
both of which are mutually exclusive of the
.B context=
option.  This means you
can use fscontext and defcontext with each other, but neither can be used with
context.

The
.B fscontext=
option works for all filesystems, regardless of their xattr
support.  The fscontext option sets the overarching filesystem label to a
specific security context.  This filesystem label is separate from the
individual labels on the files.  It represents the entire filesystem for
certain kinds of permission checks, such as during mount or file creation.
Individual file labels are still obtained from the xattrs on the files
themselves.  The context option actually sets the aggregate context that
fscontext provides, in addition to supplying the same label for individual
files.

You can set the default security context for unlabeled files using
.B defcontext=
option.  This overrides the value set for unlabeled files in the policy and requires a
filesystem that supports xattr labeling.

The
.B rootcontext=
option allows you to explicitly label the root inode of a FS being mounted
before that FS or inode becomes visible to userspace.  This was found to be
useful for things like stateless Linux.

Note that the kernel rejects any remount request that includes the context
option, \fBeven\fP when unchanged from the current context.

.BR "Warning: the \fIcontext\fP value might contain commas" ,
in which case the value has to be properly quoted, otherwise
.BR mount (8)
will interpret the comma as a separator between mount options.  Don't forget that
the shell strips off quotes and thus
.BR "double quoting is required" .
For example:
.RS
.RS
.sp
.nf
.B mount \-t tmpfs none /mnt \-o \e
.B \ \ 'context="system_u:object_r:tmp_t:s0:c127,c456",noexec'
.fi
.sp
.RE
For more details, see
.BR selinux (8).
.RE

.TP
.B defaults
Use the default options:
.BR rw ", " suid ", " dev ", " exec ", " auto ", " nouser ", and " async .

Note that the real set of all default mount options depends on the kernel
and filesystem type.  See the beginning of this section for more details.
.TP
.B dev
Interpret character or block special devices on the filesystem.
.TP
.B nodev
Do not interpret character or block special devices on the filesystem.
.TP
.B diratime
Update directory inode access times on this filesystem.  This is the default.
(This option is ignored when \fBnoatime\fR is set.)
.TP
.B nodiratime
Do not update directory inode access times on this filesystem.
(This option is implied when \fBnoatime\fR is set.)
.TP
.B dirsync
All directory updates within the filesystem should be done synchronously.
This affects the following system calls: creat, link, unlink, symlink,
mkdir, rmdir, mknod and rename.
.TP
.B exec
Permit execution of binaries.
.TP
.B noexec
Do not permit direct execution of any binaries on the mounted filesystem.
.TP
.B group
Allow an ordinary user to mount the filesystem if one
of that user's groups matches the group of the device.
This option implies the options
.BR nosuid " and " nodev
(unless overridden by subsequent options, as in the option line
.BR group,dev,suid ).
.TP
.B iversion
Every time the inode is modified, the i_version field will be incremented.
.TP
.B noiversion
Do not increment the i_version inode field.
.TP
.B mand
Allow mandatory locks on this filesystem.  See
.BR fcntl (2).
.TP
.B nomand
Do not allow mandatory locks on this filesystem.
.TP
.B _netdev
The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
.TP
.B nofail
Do not report errors for this device if it does not exist.
.TP
.B relatime
Update inode access times relative to modify or change time.  Access
time is only updated if the previous access time was earlier than the
current modify or change time.  (Similar to \fB\%noatime\fR, but it doesn't
break \fBmutt\fR or other applications that need to know if a file has been
read since the last time it was modified.)

Since Linux 2.6.30, the kernel defaults to the behavior provided by this
option (unless
.B \%noatime
was specified), and the
.B \%strictatime
option is required to obtain traditional semantics.  In addition, since Linux
2.6.30, the file's last access time is always updated if it is more than 1
day old.
.TP
.B norelatime
Do not use the
.B relatime
feature.  See also the
.B strictatime
mount option.
.TP
.B strictatime
Allows to explicitly request full atime updates.  This makes it
possible for the kernel to default to
.B \%relatime
or
.B \%noatime
but still allow userspace to override it.  For more details about the default
system mount options see
.IR /proc/mounts .
.TP
.B nostrictatime
Use the kernel's default behavior for inode access time updates.
.TP
.B lazytime
Only update times (atime, mtime, ctime) on the in-memory version of the file inode.

This mount option significantly reduces writes to the inode table for
workloads that perform frequent random writes to preallocated files.

The on-disk timestamps are updated only when:
.RS
.IP - 2
the inode needs to be updated for some change unrelated to file timestamps
.IP -
the application employs
.BR fsync (2),
.BR syncfs (2),
or
.BR sync (2)
.IP -
an undeleted inode is evicted from memory
.IP -
more than 24 hours have passed since the i-node was written to disk.
.RE
.sp
.TP
.B nolazytime
Do not use the lazytime feature.
.TP
.B suid
Honor set-user-ID and set-group-ID bits or file capabilities when
executing programs from this filesystem.
.TP
.B nosuid
Do not honor set-user-ID and set-group-ID bits or file capabilities when
executing programs from this filesystem.
.TP
.B silent
Turn on the silent flag.
.TP
.B loud
Turn off the silent flag.
.TP
.B owner
Allow an ordinary user to mount the filesystem if that
user is the owner of the device.
This option implies the options
.BR nosuid " and " nodev
(unless overridden by subsequent options, as in the option line
.BR owner,dev,suid ).
.TP
.B remount
Attempt to remount an already-mounted filesystem.  This is commonly
used to change the mount flags for a filesystem, especially to make a
readonly filesystem writable.  It does not change device or mount point.

The remount operation together with the
.B bind
flag has special semantics. See above, the subsection \fBBind mounts\fR.

The remount functionality follows the standard way the
.B mount
command works
with options from
.IR fstab .
This means that \fBmount\fR does not read
.I fstab
(or
.IR mtab )
only when both
.I device
and
.I dir
are specified.
.sp
.in +4
.B "mount \-o remount,rw /dev/foo /dir"
.in
.sp
After this call all old mount options are replaced and arbitrary stuff from
.I fstab
(or
.IR mtab )
is ignored, except the loop= option which is internally
generated and maintained by the mount command.
.sp
.in +4
.B "mount \-o remount,rw  /dir"
.in
.sp
After this call, mount reads
.I fstab
and merges these options with
the options from the command line (\fB\-o\fR).
If no mountpoint is found in
.IR fstab ,
then a remount with unspecified source is
allowed.
.sp
.B mount
allows the use of \fB\-\-all\fR to remount all already mounted filesystems
which match a specified filter (\fB\-O\fR and \fB\-t\fR).  For example:
.sp
.in +4
.B "mount \-\-all \-o remount,ro \-t vfat"
.in
.sp
remounts all already mounted vfat filesystems in read-only mode. Each of the
filesystems is remounted by "mount \-o remount,ro /dir" semantic.
This means the
.B mount
command reads
.I fstab
or
.I mtab
and merges these options with the options
from the command line.
.TP
.B ro
Mount the filesystem read-only.
.TP
.B rw
Mount the filesystem read-write.
.TP
.B sync
All I/O to the filesystem should be done synchronously.  In the case of
media with a limited number of write cycles
(e.g.\& some flash drives), \fBsync\fR may cause life-cycle shortening.
.TP
.B user
Allow an ordinary user to mount the filesystem.
The name of the mounting user is written to the
.I mtab
file (or to the private
libmount file in
.I /run/mount
on systems without a regular
.IR mtab )
so that this
same user can unmount the filesystem again.
This option implies the options
.BR noexec ", " nosuid ", and " nodev
(unless overridden by subsequent options, as in the option line
.BR user,exec,dev,suid ).
.TP
.B nouser
Forbid an ordinary user to mount the filesystem.
This is the default; it does not imply any other options.
.TP
.B users
Allow any user to mount and to unmount the filesystem, even
when some other ordinary user mounted it.
This option implies the options
.BR noexec ", " nosuid ", and " nodev
(unless overridden by subsequent options, as in the option line
.BR users,exec,dev,suid ).
.TP
.B X-*
All options prefixed with "X-" are interpreted as comments or as userspace
application-specific options.
These options are not stored in user space (e.g.,
.I mtab
file),
nor sent to the mount.\fItype\fR helpers nor to the
.BR mount (2)
system call.  The suggested format is \fBX-\fIappname\fR.\fIoption\fR.
.TP
.B x-*
The same as \fBX-*\fR options, but stored permanently in user space.
This means the options are also available for
.B umount
or other operations.  Note
that maintaining  mount options in user space is tricky,
because it's necessary use
libmount-based tools and there is no guarantee that the options will be always
available (for example after a move mount operation or in unshared namespace).

Note that before util-linux v2.30 the x-* options have not been maintained by
libmount and stored in user space (functionality was the same as for X-* now),
but due to the growing number of use-cases (in initrd, systemd etc.) the
functionality has been extended to keep existing
.I fstab
configurations usable
without a change.
.TP
.BR X-mount.mkdir [ = \fImode\fR ]
Allow to make a target directory (mountpoint) if it does not exit yet.
The optional argument
.I mode
specifies the filesystem access mode used for
.BR mkdir (2)
in octal notation.  The default mode is 0755.  This functionality is supported
only for root users or when mount executed without suid permissions.  The option
is also supported as x-mount.mkdir, this notation is deprecated since v2.30.
.TP
.B nosymfollow
Do not follow symlinks when resolving paths.  Symlinks can still be created,
and
.BR readlink (1),
.BR readlink (2),
.BR realpath (1)
and
.BR realpath (3)
all still work properly.

.SH FILESYSTEM-SPECIFIC MOUNT OPTIONS
This section lists options that are specific to particular filesystems.
Where possible, you should first consult filesystem-specific manual pages
for details.
Some of those pages are listed in the following table.
.TS
lb lb
l l.
Filesystem(s)	Manual page
btrfs	\fBbtrfs\fP(5)
cifs	\fBmount.cifs\fP(8)
ext2, ext3, ext4	\fBext4\fP(5)
fuse	\fBfuse\fP(8)
nfs	\fBnfs\fP(5)
tmpfs	\fBtmpfs\fP(5)
xfs	\fBxfs\fP(5)
.TE
.PP
Note that some of the pages listed above might be available only
after you install the respective userland tools.
.PP
The following options apply only to certain filesystems.
We sort them by filesystem.
All options follow the
.B \-o
flag.
.PP
What options are supported depends a bit on the running kernel.
Further information may be available in filesystem-specific
files in the kernel source subdirectory
.IR Documentation/filesystems .
.\"
.SS "Mount options for adfs"
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
Set the owner and group of the files in the filesystem (default: uid=gid=0).
.TP
\fBownmask=\fP\,\fIvalue\fP and \fBothmask=\fP\,\fIvalue\fP
Set the permission mask for ADFS 'owner' permissions and 'other' permissions,
respectively (default: 0700 and 0077, respectively).
See also
.IR /usr/src/linux/Documentation/filesystems/adfs.rst .

.SS "Mount options for affs"
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
Set the owner and group of the root of the filesystem (default: uid=gid=0,
but with option
.B uid
or
.B gid
without specified value, the UID and GID of the current process are taken).
.TP
\fBsetuid=\fP\,\fIvalue\fP and \fBsetgid=\fP\,\fIvalue\fP
Set the owner and group of all files.
.TP
.BI mode= value
Set the mode of all files to
.IR value " & 0777"
disregarding the original permissions.
Add search permission to directories that have read permission.
The value is given in octal.
.TP
.B protect
Do not allow any changes to the protection bits on the filesystem.
.TP
.B usemp
Set UID and GID of the root of the filesystem to the UID and GID
of the mount point upon the first sync or umount, and then
clear this option.  Strange...
.TP
.B verbose
Print an informational message for each successful mount.
.TP
.BI prefix= string
Prefix used before volume name, when following a link.
.TP
.BI volume= string
Prefix (of length at most 30) used before '/' when following a symbolic link.
.TP
.BI reserved= value
(Default: 2.) Number of unused blocks at the start of the device.
.TP
.BI root= value
Give explicitly the location of the root block.
.TP
.BI bs= value
Give blocksize.  Allowed values are 512, 1024, 2048, 4096.
.TP
.BR grpquota | noquota | quota | usrquota
These options are accepted but ignored.
(However, quota utilities may react to such strings in
.IR /etc/fstab .)

.SS "Mount options for debugfs"
The debugfs filesystem is a pseudo filesystem, traditionally mounted on
.IR /sys/kernel/debug .
.\" or just /debug
.\" present since 2.6.11
As of kernel version 3.4, debugfs has the following options:
.TP
.BI uid= n ", gid=" n
Set the owner and group of the mountpoint.
.TP
.BI mode= value
Sets the mode of the mountpoint.

.SS "Mount options for devpts"
The devpts filesystem is a pseudo filesystem, traditionally mounted on
.IR /dev/pts .
In order to acquire a pseudo terminal, a process opens
.IR /dev/ptmx ;
the number of the pseudo terminal is then made available to the process
and the pseudo terminal slave can be accessed as
.IR /dev/pts/ <number>.
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
This sets the owner or the group of newly created pseudo terminals to
the specified values.  When nothing is specified, they will
be set to the UID and GID of the creating process.
For example, if there is a tty group with GID 5, then
.B gid=5
will cause newly created pseudo terminals to belong to the tty group.
.TP
.BI mode= value
Set the mode of newly created pseudo terminals to the specified value.
The default is 0600.
A value of
.B mode=620
and
.B gid=5
makes "mesg y" the default on newly created pseudo terminals.
.TP
\fBnewinstance
Create a private instance of the devpts filesystem, such that
indices of pseudo terminals allocated in this new instance are
independent of indices created in other instances of devpts.

All mounts of devpts without this
.B newinstance
option share the same set of pseudo terminal indices (i.e., legacy mode).
Each mount of devpts with the
.B newinstance
option has a private set of pseudo terminal indices.

This option is mainly used to support containers in the
Linux kernel.  It is implemented in Linux kernel versions
starting with 2.6.29.  Further, this mount option is valid
only if CONFIG_DEVPTS_MULTIPLE_INSTANCES is enabled in the
kernel configuration.

To use this option effectively,
.I /dev/ptmx
must be a symbolic link to
.IR pts/ptmx .
See
.I Documentation/filesystems/devpts.txt
in the Linux kernel source tree for details.
.TP
.BI ptmxmode= value

Set the mode for the new
.I ptmx
device node in the devpts filesystem.

With the support for multiple instances of devpts (see
.B newinstance
option above), each instance has a private
.I ptmx
node in the root of the devpts filesystem (typically
.IR /dev/pts/ptmx ).

For compatibility with older versions of the kernel, the
default mode of the new
.I ptmx
node is 0000.
.BI ptmxmode= value
specifies a more useful mode for the
.I ptmx
node and is highly recommended when the
.B newinstance
option is specified.

This option is only implemented in Linux kernel versions
starting with 2.6.29.  Further, this option is valid only if
CONFIG_DEVPTS_MULTIPLE_INSTANCES is enabled in the kernel
configuration.

.SS "Mount options for fat"
(Note:
.I fat
is not a separate filesystem, but a common part of the
.IR msdos ,
.I umsdos
and
.I vfat
filesystems.)
.TP
.BR blocksize= { 512 | 1024 | 2048 }
Set blocksize (default 512).  This option is obsolete.
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
Set the owner and group of all files.
(Default: the UID and GID of the current process.)
.TP
.BI umask= value
Set the umask (the bitmask of the permissions that are
.B not
present).  The default is the umask of the current process.
The value is given in octal.
.TP
.BI dmask= value
Set the umask applied to directories only.
The default is the umask of the current process.
The value is given in octal.
.TP
.BI fmask= value
Set the umask applied to regular files only.
The default is the umask of the current process.
The value is given in octal.
.TP
.BI allow_utime= value
This option controls the permission check of mtime/atime.
.RS
.TP
.B 20
If current process is in group of file's group ID, you can change timestamp.
.TP
.B 2
Other users can change timestamp.
.PP
The default is set from `dmask' option. (If the directory is writable,
.BR utime (2)
is also allowed.  I.e.\& \s+3~\s0dmask & 022)

Normally
.BR utime (2)
checks that the current process is owner of the file, or that it has the
.B CAP_FOWNER
capability.  But FAT filesystems don't have UID/GID on disk, so the
normal check is too inflexible.  With this option you can relax it.
.RE
.TP
.BI check= value
Three different levels of pickiness can be chosen:
.RS
.TP
.BR r [ elaxed ]
Upper and lower case are accepted and equivalent, long name parts are
truncated (e.g.\&
.I verylongname.foobar
becomes
.IR verylong.foo ),
leading and embedded spaces are accepted in each name part (name and extension).
.TP
.BR n [ ormal ]
Like "relaxed", but many special characters (*, ?, <, spaces, etc.) are
rejected.  This is the default.
.TP
.BR s [ trict ]
Like "normal", but names that contain long parts or special characters
that are sometimes used on Linux but are not accepted by MS-DOS
(+, =, etc.) are rejected.
.RE
.TP
.BI codepage= value
Sets the codepage for converting to shortname characters on FAT
and VFAT filesystems.  By default, codepage 437 is used.
.TP
.BI conv= mode
This option is obsolete and may fail or be ignored.
.TP
.BI cvf_format= module
Forces the driver to use the CVF (Compressed Volume File) module
.RI cvf_ module
instead of auto-detection.  If the kernel supports kmod, the
cvf_format=xxx option also controls on-demand CVF module loading.
This option is obsolete.
.TP
.BI cvf_option= option
Option passed to the CVF module.  This option is obsolete.
.TP
.B debug
Turn on the
.I debug
flag.  A version string and a list of filesystem parameters will be
printed (these data are also printed if the parameters appear to be
inconsistent).
.TP
.B discard
If set, causes discard/TRIM commands to be issued to the block device
when blocks are freed.  This is useful for SSD devices and
sparse/thinly-provisioned LUNs.
.TP
.B dos1xfloppy
If set, use a fallback default BIOS Parameter Block configuration, determined
by backing device size.  These static parameters match defaults assumed by DOS
1.x for 160 kiB, 180 kiB, 320 kiB, and 360 kiB floppies and floppy images.
.TP
.BR errors= { panic | continue | remount-ro }
Specify FAT behavior on critical errors: panic, continue without doing
anything, or remount the partition in read-only mode (default behavior).
.TP
.BR fat= { 12 | 16 | 32 }
Specify a 12, 16 or 32 bit fat.  This overrides
the automatic FAT type detection routine.  Use with caution!
.TP
.BI iocharset= value
Character set to use for converting between 8 bit characters
and 16 bit Unicode characters.  The default is iso8859-1.
Long filenames are stored on disk in Unicode format.
.TP
.BR nfs= { stale_rw | nostale_ro }
Enable this only if you want to export the FAT filesystem over NFS.

.BR stale_rw :
This option maintains an index (cache) of directory inodes which is used by the
nfs-related code to improve look-ups.  Full file operations (read/write) over
NFS are supported but with cache eviction at NFS server, this could result in
spurious
.B ESTALE
errors.

.BR nostale_ro :
This option bases the inode number and file handle
on the on-disk location of a file in the FAT directory entry.
This ensures that
.B ESTALE
will not be returned after a file is
evicted from the inode cache.  However, it means that operations
such as rename, create and unlink could cause file handles that
previously pointed at one file to point at a different file,
potentially causing data corruption.  For this reason, this
option also mounts the filesystem readonly.

To maintain backward compatibility, '\-o nfs' is also accepted,
defaulting to
.BR stale_rw .
.TP
.B tz=UTC
This option disables the conversion of timestamps
between local time (as used by Windows on FAT) and UTC
(which Linux uses internally).  This is particularly
useful when mounting devices (like digital cameras)
that are set to UTC in order to avoid the pitfalls of
local time.
.TP
.BI time_offset= minutes
Set offset for conversion of timestamps from local time used by FAT to UTC.
I.e.,
.I minutes
will be subtracted from each timestamp to convert it to UTC used
internally by Linux.  This is useful when the time zone set in the kernel via
.BR settimeofday (2)
is not the time zone used by the filesystem.  Note
that this option still does not provide correct time stamps in all cases in
presence of DST - time stamps in a different DST setting will be off by one
hour.
.TP
.B quiet
Turn on the
.I quiet
flag.  Attempts to chown or chmod files do not return errors,
although they fail.  Use with caution!
.TP
.B rodir
FAT has the ATTR_RO (read-only) attribute.  On Windows, the ATTR_RO of the
directory will just be ignored, and is used only by applications as a flag
(e.g.\& it's set for the customized folder).

If you want to use ATTR_RO as read-only flag even for the directory, set this
option.
.TP
.B showexec
If set, the execute permission bits of the file will be allowed only if
the extension part of the name is \&.EXE, \&.COM, or \&.BAT.  Not set by default.
.TP
.B sys_immutable
If set, ATTR_SYS attribute on FAT is handled as IMMUTABLE flag on Linux.
Not set by default.
.TP
.B flush
If set, the filesystem will try to flush to disk more early than normal.
Not set by default.
.TP
.B usefree
Use the "free clusters" value stored on FSINFO.  It'll
be used to determine number of free clusters without
scanning disk.  But it's not used by default, because
recent Windows don't update it correctly in some
case.  If you are sure the "free clusters" on FSINFO is
correct, by this option you can avoid scanning disk.
.TP
.BR dots ", " nodots ", " dotsOK= [ yes | no ]
Various misguided attempts to force Unix or DOS conventions
onto a FAT filesystem.

.SS "Mount options for hfs"
.TP
.BI creator= cccc ", type=" cccc
Set the creator/type values as shown by the MacOS finder
used for creating new files.  Default values: '????'.
.TP
.BI uid= n ", gid=" n
Set the owner and group of all files.
(Default: the UID and GID of the current process.)
.TP
.BI dir_umask= n ", file_umask=" n ", umask=" n
Set the umask used for all directories, all regular files, or all
files and directories.  Defaults to the umask of the current process.
.TP
.BI session= n
Select the CDROM session to mount.
Defaults to leaving that decision to the CDROM driver.
This option will fail with anything but a CDROM as underlying device.
.TP
.BI part= n
Select partition number n from the device.
Only makes sense for CDROMs.
Defaults to not parsing the partition table at all.
.TP
.B quiet
Don't complain about invalid mount options.

.SS "Mount options for hpfs"
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
Set the owner and group of all files. (Default: the UID and GID
of the current process.)
.TP
.BI umask= value
Set the umask (the bitmask of the permissions that are
.B not
present).  The default is the umask of the current process.
The value is given in octal.
.TP
.BR case= { lower | asis }
Convert all files names to lower case, or leave them.
(Default:
.BR case=lower .)
.TP
.BI conv= mode
This option is obsolete and may fail or being ignored.
.TP
.B nocheck
Do not abort mounting when certain consistency checks fail.

.SS "Mount options for iso9660"
ISO 9660 is a standard describing a filesystem structure to be used
on CD-ROMs. (This filesystem type is also seen on some DVDs.  See also the
.I udf
filesystem.)

Normal
.I iso9660
filenames appear in an 8.3 format (i.e., DOS-like restrictions on filename
length), and in addition all characters are in upper case.  Also there is
no field for file ownership, protection, number of links, provision for
block/character devices, etc.

Rock Ridge is an extension to iso9660 that provides all of these UNIX-like
features.  Basically there are extensions to each directory record that
supply all of the additional information, and when Rock Ridge is in use,
the filesystem is indistinguishable from a normal UNIX filesystem (except
that it is read-only, of course).
.TP
.B norock
Disable the use of Rock Ridge extensions, even if available.  Cf.\&
.BR map .
.TP
.B nojoliet
Disable the use of Microsoft Joliet extensions, even if available.  Cf.\&
.BR map .
.TP
.BR check= { r [ elaxed ]| s [ trict ]}
With
.BR check=relaxed ,
a filename is first converted to lower case before doing the lookup.
This is probably only meaningful together with
.B norock
and
.BR map=normal .
(Default:
.BR check=strict .)
.TP
\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
Give all files in the filesystem the indicated user or group id,
possibly overriding the information found in the Rock Ridge extensions.
(Default:
.BR uid=0,gid=0 .)
.TP
.BR map= { n [ ormal ]| o [ ff ]| a [ corn ]}
For non-Rock Ridge volumes, normal name translation maps upper
to lower case ASCII, drops a trailing `;1', and converts `;' to `.'.
With
.B map=off
no name translation is done.  See
.BR norock .
(Default:
.BR map=normal .)
.B map=acorn
is like
.B map=normal
but also apply Acorn extensions if present.
.TP
.BI mode= value
For non-Rock Ridge volumes, give all files the indicated mode.
(Default: read and execute permission for everybody.)
Octal mode values require a leading 0.
.TP
.B unhide
Also show hidden and associated files.
(If the ordinary files and the associated or hidden files have
the same filenames, this may make the ordinary files inaccessible.)
.TP
.BR block= { 512 | 1024 | 2048 }
Set the block size to the indicated value.
(Default:
.BR block=1024 .)
.TP
.BI conv= mode
This option is obsolete and may fail or being ignored.
.TP
.B cruft
If the high byte of the file length contains other garbage,
set this mount option to ignore the high order bits of the file length.
This implies that a file cannot be larger than 16\ MB.
.TP
.BI session= x
Select number of session on multisession CD.
.TP
.BI sbsector= xxx
Session begins from sector xxx.
.LP
The following options are the same as for vfat and specifying them only makes
sense when using discs encoded using Microsoft's Joliet extensions.
.TP
.BI iocharset= value
Character set to use for converting 16 bit Unicode characters on CD
to 8 bit characters.  The default is iso8859-1.
.TP
.B utf8
Convert 16 bit Unicode characters on CD to UTF-8.

.SS "Mount options for jfs"
.TP
.BI iocharset= name
Character set to use for converting from Unicode to ASCII.  The default is
to do no conversion.  Use
.B iocharset=utf8
for UTF8 translations.  This requires CONFIG_NLS_UTF8 to be set in
the kernel
.I ".config"
file.
.TP
.BI resize= value
Resize the volume to
.I value
blocks.  JFS only supports growing a volume, not shrinking it.  This option
is only valid during a remount, when the volume is mounted read-write.  The
.B resize
keyword with no value will grow the volume to the full size of the partition.
.TP
.B nointegrity
Do not write to the journal.  The primary use of this option is to allow
for higher performance when restoring a volume from backup media.  The
integrity of the volume is not guaranteed if the system abnormally ends.
.TP
.B integrity
Default.  Commit metadata changes to the journal.  Use this option to remount
a volume where the
.B nointegrity
option was previously specified in order to restore normal behavior.
.TP
.BR errors= { continue | remount-ro | panic }
Define the behavior when an error is encountered.
(Either ignore errors and just mark the filesystem erroneous and continue,
or remount the filesystem read-only, or panic and halt the system.)
.TP
.BR noquota | quota | usrquota | grpquota
These options are accepted but ignored.

.SS "Mount options for msdos"
See mount options for fat.
If the
.I msdos
filesystem detects an inconsistency, it reports an error and sets the file
system read-only.  The filesystem can be made writable again by remounting
it.

.SS "Mount options for ncpfs"
Just like
.IR nfs ", the " ncpfs
implementation expects a binary argument (a
.IR "struct ncp_mount_data" )
to the mount system call.  This argument is constructed by
.BR ncpmount (8)
and the current version of
.B mount
(2.12) does not know anything about ncpfs.

.SS "Mount options for ntfs"
.TP
.BI iocharset= name
Character set to use when returning file names.
Unlike VFAT, NTFS suppresses names that contain
nonconvertible characters.  Deprecated.
.TP
.BI nls= name
New name for the option earlier called
.IR iocharset .
.TP
.B utf8
Use UTF-8 for converting file names.
.TP
.BR uni_xlate= { 0 | 1 | 2 }
For 0 (or `no' or `false'), do not use escape sequences
for unknown Unicode characters.
For 1 (or `yes' or `true') or 2, use vfat-style 4-byte escape sequences
starting with ":".  Here 2 give a little-endian encoding
and 1 a byteswapped bigendian encoding.
.TP
.B posix=[0|1]
If enabled (posix=1), the filesystem distinguishes between
upper and lower case.  The 8.3 alias names are presented as
hard links instead of being suppressed.  This option is obsolete.
.TP
\fBuid=\fP\,\fIvalue\fP, \fBgid=\fP\,\fIvalue\fP and \fBumask=\fP\,\fIvalue\fP
Set the file permission on the filesystem.
The umask value is given in octal.
By default, the files are owned by root and not readable by somebody else.

.SS "Mount options for overlay"
Since Linux 3.18 the overlay pseudo filesystem implements a union mount for
other filesystems.

An overlay filesystem combines two filesystems - an \fBupper\fR filesystem and
a \fBlower\fR filesystem.  When a name exists in both filesystems, the object
in the upper filesystem is visible while the object in the lower filesystem is
either hidden or, in the case of directories, merged with the upper object.

The lower filesystem can be any filesystem supported by Linux and does not need
to be writable.  The lower filesystem can even be another overlayfs.  The upper
filesystem will normally be writable and if it is it must support the creation
of trusted.* extended attributes, and must provide a valid d_type in readdir
responses, so NFS is not suitable.

A read-only overlay of two read-only filesystems may use any filesystem type.
The options \fBlowerdir\fR and \fBupperdir\fR are combined into a merged
directory by using:

.RS
.br
.nf
.B "mount \-t overlay  overlay  \e"
.B "  \-olowerdir=/lower,upperdir=/upper,workdir=/work  /merged"
.fi
.br
.RE

.TP
.BI lowerdir= directory
Any filesystem, does not need to be on a writable filesystem.
.TP
.BI upperdir= directory
The upperdir is normally on a writable filesystem.
.TP
.BI workdir= directory
The workdir needs to be an empty directory on the same filesystem as upperdir.

.SS "Mount options for reiserfs"
Reiserfs is a journaling filesystem.
.TP
.B conv
Instructs version 3.6 reiserfs software to mount a version 3.5 filesystem,
using the 3.6 format for newly created objects.  This filesystem will no
longer be compatible with reiserfs 3.5 tools.
.TP
.BR hash= { rupasov | tea | r5 | detect }
Choose which hash function reiserfs will use to find files within directories.
.RS
.TP
.B rupasov
A hash invented by Yury Yu.\& Rupasov.  It is fast and preserves locality,
mapping lexicographically close file names to close hash values.
This option should not be used, as it causes a high probability of hash
collisions.
.TP
.B tea
A Davis-Meyer function implemented by Jeremy Fitzhardinge.
It uses hash permuting bits in the name.  It gets high randomness
and, therefore, low probability of hash collisions at some CPU cost.
This may be used if EHASHCOLLISION errors are experienced with the r5 hash.
.TP
.B r5
A modified version of the rupasov hash.  It is used by default and is
the best choice unless the filesystem has huge directories and
unusual file-name patterns.
.TP
.B detect
Instructs
.I mount
to detect which hash function is in use by examining
the filesystem being mounted, and to write this information into
the reiserfs superblock.  This is only useful on the first mount of
an old format filesystem.
.RE
.TP
.B hashed_relocation
Tunes the block allocator.  This may provide performance improvements
in some situations.
.TP
.B no_unhashed_relocation
Tunes the block allocator.  This may provide performance improvements
in some situations.
.TP
.B noborder
Disable the border allocator algorithm invented by Yury Yu.\& Rupasov.
This may provide performance improvements in some situations.
.TP
.B nolog
Disable journaling.  This will provide slight performance improvements in
some situations at the cost of losing reiserfs's fast recovery from crashes.
Even with this option turned on, reiserfs still performs all journaling
operations, save for actual writes into its journaling area.  Implementation
of
.I nolog
is a work in progress.
.TP
.B notail
By default, reiserfs stores small files and `file tails' directly into its
tree.  This confuses some utilities such as
.BR LILO (8).
This option is used to disable packing of files into the tree.
.TP
.B replayonly
Replay the transactions which are in the journal, but do not actually
mount the filesystem.  Mainly used by
.IR reiserfsck .
.TP
.BI resize= number
A remount option which permits online expansion of reiserfs partitions.
Instructs reiserfs to assume that the device has
.I number
blocks.
This option is designed for use with devices which are under logical
volume management (LVM).
There is a special
.I resizer
utility which can be obtained from
.IR ftp://ftp.namesys.com/pub/reiserfsprogs .
.TP
.B user_xattr
Enable Extended User Attributes.  See the
.BR attr (1)
manual page.
.TP
.B acl
Enable POSIX Access Control Lists.  See the
.BR acl (5)
manual page.
.TP
.BR barrier=none " / " barrier=flush
This disables / enables the use of write barriers in the journaling code.
barrier=none disables, barrier=flush enables (default).  This also requires an
IO stack which can support barriers, and if reiserfs gets an error on a barrier
write, it will disable barriers again with a warning.  Write barriers enforce
proper on-disk ordering of journal commits, making volatile disk write caches
safe to use, at some performance penalty.  If your disks are battery-backed in
one way or another, disabling barriers may safely improve performance.

.SS "Mount options for ubifs"
UBIFS is a flash filesystem which works on top of UBI volumes.  Note that
\fBatime\fR is not supported and is always turned off.
.TP
The device name may be specified as
.PP
.RS
.B ubiX_Y
UBI device number
.BR X ,
volume number
.B Y
.TP
.B ubiY
UBI device number
.BR 0 ,
volume number
.B Y
.TP
.B ubiX:NAME
UBI device number
.BR X ,
volume with name
.B NAME
.TP
.B ubi:NAME
UBI device number
.BR 0 ,
volume with name
.B NAME
.RE
.PP
Alternative
.B !
separator may be used instead of
.BR : .
.TP
The following mount options are available:
.TP
.B bulk_read
Enable bulk-read.  VFS read-ahead is disabled because it slows down the filesystem.  Bulk-Read is an internal optimization.  Some flashes may read faster if
the data are read at one go, rather than at several read requests.  For
example, OneNAND can do "read-while-load" if it reads more than one NAND page.
.TP
.B no_bulk_read
Do not bulk-read.  This is the default.
.TP
.B chk_data_crc
Check data CRC-32 checksums.  This is the default.
.TP
.BR no_chk_data_crc .
Do not check data CRC-32 checksums.  With this option, the filesystem does not
check CRC-32 checksum for data, but it does check it for the internal indexing
information.  This option only affects reading, not writing.  CRC-32 is always
calculated when writing the data.
.TP
.BR compr= { none | lzo | zlib }
Select the default compressor which is used when new files are written.  It is
still possible to read compressed files if mounted with the
.B none
option.

.SS "Mount options for udf"
UDF is the "Universal Disk Format" filesystem defined by OSTA, the Optical
Storage Technology Association, and is often used for DVD-ROM, frequently
in the form of a hybrid UDF/ISO-9660 filesystem. It is, however,
perfectly usable by itself on disk drives, flash drives and other block devices.
See also
.IR iso9660 .
.TP
.B uid=
Make all files in the filesystem belong to the given user.
uid=forget can be specified independently of (or usually in
addition to) uid=<user> and results in UDF
not storing uids to the media. In fact the recorded uid
is the 32-bit overflow uid \-1 as defined by the UDF standard.
The value is given as either <user> which is a valid user name or the corresponding
decimal user id, or the special string "forget".
.TP
.B gid=
Make all files in the filesystem belong to the given group.
gid=forget can be specified independently of (or usually in
addition to) gid=<group> and results in UDF
not storing gids to the media. In fact the recorded gid
is the 32-bit overflow gid \-1 as defined by the UDF standard.
The value is given as either <group> which is a valid group name or the corresponding
decimal group id, or the special string "forget".
.TP
.B umask=
Mask out the given permissions from all inodes read from the filesystem.
The value is given in octal.
.TP
.B mode=
If mode= is set the permissions of all non-directory inodes read from the
filesystem will be set to the given mode. The value is given in octal.
.TP
.B dmode=
If dmode= is set the permissions of all directory inodes read from the
filesystem will be set to the given dmode. The value is given in octal.
.TP
.B bs=
Set the block size. Default value prior to kernel version 2.6.30 was
2048. Since 2.6.30 and prior to 4.11 it was logical device block size with
fallback to 2048. Since 4.11 it is logical block size with fallback to
any valid block size between logical device block size and 4096.

For other details see the \fBmkudffs\fP(8) 2.0+ manpage, sections
\fBCOMPATIBILITY\fP and \fBBLOCK SIZE\fP.
.TP
.B unhide
Show otherwise hidden files.
.TP
.B undelete
Show deleted files in lists.
.TP
.B adinicb
Embed data in the inode. (default)
.TP
.B noadinicb
Don't embed data in the inode.
.TP
.B shortad
Use short UDF address descriptors.
.TP
.B longad
Use long UDF address descriptors. (default)
.TP
.B nostrict
Unset strict conformance.
.TP
.B iocharset=
Set the NLS character set. This requires kernel compiled with CONFIG_UDF_NLS option.
.TP
.B utf8
Set the UTF-8 character set.
.SS Mount options for debugging and disaster recovery
.TP
.B novrs
Ignore the Volume Recognition Sequence and attempt to mount anyway.
.TP
.B session=
Select the session number for multi-session recorded optical media. (default= last session)
.TP
.B anchor=
Override standard anchor location. (default= 256)
.TP
.B lastblock=
Set the last block of the filesystem.
.SS Unused historical mount options that may be encountered and should be removed
.TP
.B uid=ignore
Ignored, use uid=<user> instead.
.TP
.B gid=ignore
Ignored, use gid=<group> instead.
.TP
.B volume=
Unimplemented and ignored.
.TP
.B partition=
Unimplemented and ignored.
.TP
.B fileset=
Unimplemented and ignored.
.TP
.B rootdir=
Unimplemented and ignored.

.SS "Mount options for ufs"
.TP
.BI ufstype= value
UFS is a filesystem widely used in different operating systems.
The problem are differences among implementations.  Features of some
implementations are undocumented, so its hard to recognize the
type of ufs automatically.
That's why the user must specify the type of ufs by mount option.
Possible values are:
.RS
.TP
.B old
Old format of ufs, this is the default, read only.
(Don't forget to give the \-r option.)
.TP
.B 44bsd
For filesystems created by a BSD-like system (NetBSD, FreeBSD, OpenBSD).
.TP
.B ufs2
Used in FreeBSD 5.x supported as read-write.
.TP
.B 5xbsd
Synonym for ufs2.
.TP
.B sun
For filesystems created by SunOS or Solaris on Sparc.
.TP
.B sunx86
For filesystems created by Solaris on x86.
.TP
.B hp
For filesystems created by HP-UX, read-only.
.TP
.B nextstep
For filesystems created by NeXTStep (on NeXT station) (currently read only).
.TP
.B nextstep-cd
For NextStep CDROMs (block_size == 2048), read-only.
.TP
.B openstep
For filesystems created by OpenStep (currently read only).
The same filesystem type is also used by Mac OS X.
.RE

.TP
.BI onerror= value
Set behavior on error:
.RS
.TP
.B panic
If an error is encountered, cause a kernel panic.
.TP
.RB [ lock | umount | repair ]
These mount options don't do anything at present;
when an error is encountered only a console message is printed.
.RE

.SS "Mount options for umsdos"
See mount options for msdos.
The
.B dotsOK
option is explicitly killed by
.IR umsdos .

.SS "Mount options for vfat"
First of all, the mount options for
.I fat
are recognized.
The
.B dotsOK
option is explicitly killed by
.IR vfat .
Furthermore, there are
.TP
.B uni_xlate
Translate unhandled Unicode characters to special escaped sequences.
This lets you backup and restore filenames that are created with any
Unicode characters.  Without this option, a '?' is used when no
translation is possible.  The escape character is ':' because it is
otherwise invalid on the vfat filesystem.  The escape sequence
that gets used, where u is the Unicode character,
is: ':', (u & 0x3f), ((u>>6) & 0x3f), (u>>12).
.TP
.B posix
Allow two files with names that only differ in case.
This option is obsolete.
.TP
.B nonumtail
First try to make a short name without sequence number,
before trying
.IR name\s+3~\s0num.ext .
.TP
.B utf8
UTF8 is the filesystem safe 8-bit encoding of Unicode that is used by the
console.  It can be enabled for the filesystem with this option or disabled
with utf8=0, utf8=no or utf8=false.  If `uni_xlate' gets set, UTF8 gets
disabled.
.TP
.BI shortname= mode
Defines the behavior for creation and display of filenames which fit into
8.3 characters.  If a long name for a file exists, it will always be the
preferred one for display.  There are four \fImode\fRs:
.RS
.TP
.B lower
Force the short name to lower case upon display; store a long name when
the short name is not all upper case.
.TP
.B win95
Force the short name to upper case upon display; store a long name when
the short name is not all upper case.
.TP
.B winnt
Display the short name as is; store a long name when the short name is
not all lower case or all upper case.
.TP
.B mixed
Display the short name as is; store a long name when the short name is not
all upper case.  This mode is the default since Linux 2.6.32.
.RE

.SS "Mount options for usbfs"
.TP
\fBdevuid=\fP\,\fIuid\fP and \fBdevgid=\fP\,\fIgid\fP and \fBdevmode=\fP\,\fImode\fP
Set the owner and group and mode of the device files in the usbfs filesystem
(default: uid=gid=0, mode=0644).  The mode is given in octal.
.TP
\fBbusuid=\fP\,\fIuid\fP and \fBbusgid=\fP\,\fIgid\fP and \fBbusmode=\fP\,\fImode\fP
Set the owner and group and mode of the bus directories in the usbfs
filesystem (default: uid=gid=0, mode=0555).  The mode is given in octal.
.TP
\fBlistuid=\fP\,\fIuid\fP and \fBlistgid=\fP\,\fIgid\fP and \fBlistmode=\fP\,\fImode\fP
Set the owner and group and mode of the file
.I devices
(default: uid=gid=0, mode=0444).  The mode is given in octal.

.SH DM-VERITY SUPPORT (experimental)
The device-mapper verity target provides read-only transparent integrity
checking of block devices using kernel crypto API.  The
.B mount
command can open
the dm-verity device and do the integrity verification before on the device
filesystem is mounted.  Requires libcryptsetup with in libmount (optionally via dlopen).
If libcryptsetup supports extracting the root hash of an already mounted device,
existing devices will be automatically reused in case of a match.
Mount options for dm-verity:
.TP
\fBverity.hashdevice=\fP\,\fIpath\fP
Path to the hash tree device associated with the source volume to pass to dm-verity.
.TP
\fBverity.roothash=\fP\,\fIhex\fP
Hex-encoded hash of the root of
.I verity.hashdevice
Mutually exclusive with
.I verity.roothashfile.
.TP
\fBverity.roothashfile=\fP\,\fIpath\fP
Path to file containing the hex-encoded hash of the root of
.I verity.hashdevice.
Mutually exclusive with
.I verity.roothash.
.TP
\fBverity.hashoffset=\fP\,\fIoffset\fP
If the hash tree device is embedded in the source volume,
.I offset
(default: 0) is used by dm-verity to get to the tree.
.TP
\fBverity.fecdevice=\fP\,\fIpath\fP
Path to the Forward Error Correction (FEC) device associated with the source volume to pass to dm-verity.
Optional. Requires kernel built with CONFIG_DM_VERITY_FEC.
.TP
\fBverity.fecoffset=\fP\,\fIoffset\fP
If the FEC device is embedded in the source volume,
.I offset
(default: 0) is used by dm-verity to get to the FEC area. Optional.
.TP
\fBverity.fecroots=\fP\,\fIvalue\fP
Parity bytes for FEC (default: 2). Optional.
.TP
\fBverity.roothashsig=\fP\,\fIpath\fP
Path to pkcs7 signature of root hash hex string. Requires crypt_activate_by_signed_key() from cryptsetup and
kernel built with CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG. For device reuse, signatures have to be either used by all
mounts of a device or by none. Optional.
.PP
Supported since util-linux v2.35.
.PP
For example commands:
.sp
.RS
.nf
.B mksquashfs /etc /tmp/etc.squashfs
.B dd if=/dev/zero of=/tmp/etc.hash bs=1M count=10
.B veritysetup format /tmp/etc.squashfs /tmp/etc.hash
.B openssl smime \-sign \-in <hash> \-nocerts \-inkey private.key \e
.B \-signer private.crt \-noattr \-binary \-outform der \-out /tmp/etc.p7
.B mount \-o verity.hashdevice=/tmp/etc.hash,verity.roothash=<hash>,\e
.B verity.roothashsig=/tmp/etc.p7 /tmp/etc.squashfs /mnt
.fi
.RE
.sp
create squashfs image from /etc directory, verity hash device
and mount verified filesystem image to /mnt.
The kernel will verify that the root hash is signed by a key from the kernel keyring if roothashsig is used.

.SH LOOP-DEVICE SUPPORT
One further possible type is a mount via the loop device.  For example,
the command
.RS
.sp
.B "mount /tmp/disk.img /mnt \-t vfat \-o loop=/dev/loop3"
.sp
.RE
will set up the loop device
.I /dev/loop3
to correspond to the file
.IR /tmp/disk.img ,
and then mount this device on
.IR /mnt .

If no explicit loop device is mentioned
(but just an option `\fB\-o loop\fP' is given), then
.B mount
will try to find some unused loop device and use that, for example
.RS
.sp
.B "mount /tmp/disk.img /mnt \-o loop"
.sp
.RE
The
.B mount
command
.B automatically
creates a loop device from a regular file if a filesystem type is
not specified or the filesystem is known for libblkid, for example:
.RS
.sp
.B "mount /tmp/disk.img /mnt"
.sp
.B "mount \-t ext4 /tmp/disk.img /mnt"
.sp
.RE
This type of mount knows about three options, namely
.BR loop ", " offset " and " sizelimit ,
that are really options to
.BR \%losetup (8).
(These options can be used in addition to those specific
to the filesystem type.)

Since Linux 2.6.25 auto-destruction of loop devices is supported,
meaning that any loop device allocated by
.B mount
will be freed by
.B umount
independently of
.IR /etc/mtab .

You can also free a loop device by hand, using
.BR "losetup \-d " or " umount \-d" .

Since util-linux v2.29,
.B mount
re-uses the loop device rather than
initializing a new device if the same backing file is already used for some loop
device with the same offset and sizelimit. This is necessary to avoid
a filesystem corruption.

.SH EXIT STATUS
.B mount
has the following exit status values (the bits can be ORed):
.TP
.B 0
success
.TP
.B 1
incorrect invocation or permissions
.TP
.B 2
system error (out of memory, cannot fork, no more loop devices)
.TP
.B 4
internal
.B mount
bug
.TP
.B 8
user interrupt
.TP
.B 16
problems writing or locking /etc/mtab
.TP
.B 32
mount failure
.TP
.B 64
some mount succeeded

The command \fBmount \-a\fR returns 0 (all succeeded), 32 (all failed), or 64 (some
failed, some succeeded).

.SH EXTERNAL HELPERS
The syntax of external mount helpers is:
.sp
.in +4
.BI /sbin/mount. suffix
.I spec dir
.RB [ \-sfnv ]
.RB [ \-N
.IR namespace ]
.RB [ \-o
.IR options ]
.RB [ \-t
.IR type \fB. subtype ]
.in
.sp
where the \fIsuffix\fR is the filesystem type and the \fB\-sfnvoN\fR options have
the same meaning as the normal mount options.  The \fB\-t\fR option is used for
filesystems with subtypes support (for example
.BR "/sbin/mount.fuse \-t fuse.sshfs" ).

The command \fBmount\fR does not pass the mount options
.BR unbindable ,
.BR runbindable ,
.BR private ,
.BR rprivate ,
.BR slave ,
.BR rslave ,
.BR shared ,
.BR rshared ,
.BR auto ,
.BR noauto ,
.BR comment ,
.BR x-* ,
.BR loop ,
.B offset
and
.B sizelimit
to the mount.<suffix> helpers.  All other options are used in a
comma-separated list as an argument to the \fB\-o\fR option.

.SH ENVIRONMENT
.IP LIBMOUNT_FSTAB=<path>
overrides the default location of the
.I fstab
file (ignored for suid)
.IP LIBMOUNT_MTAB=<path>
overrides the default location of the
.I mtab
file (ignored for suid)
.IP LIBMOUNT_DEBUG=all
enables libmount debug output
.IP LIBBLKID_DEBUG=all
enables libblkid debug output
.IP LOOPDEV_DEBUG=all
enables loop device setup debug output
.SH FILES
See also "\fBThe files /etc/fstab, /etc/mtab and /proc/mounts\fR" section above.
.TP 18n
.I /etc/fstab
filesystem table
.TP
.I /run/mount
libmount private runtime directory
.TP
.I /etc/mtab
table of mounted filesystems or symlink to
.I /proc/mounts
.TP
.I /etc/mtab\s+3~\s0
lock file (unused on systems with
.I mtab
symlink)
.TP
.I /etc/mtab.tmp
temporary file (unused on systems with
.I mtab
symlink)
.TP
.I /etc/filesystems
a list of filesystem types to try
.SH HISTORY
A
.B mount
command existed in Version 5 AT&T UNIX.
.SH BUGS
It is possible for a corrupted filesystem to cause a crash.
.PP
Some Linux filesystems don't support
.BR "\-o sync " and " \-o dirsync"
(the ext2, ext3, ext4, fat and vfat filesystems
.I do
support synchronous updates (a la BSD) when mounted with the
.B sync
option).
.PP
The
.B "\-o remount"
may not be able to change mount parameters (all
.IR ext2fs -specific
parameters, except
.BR sb ,
are changeable with a remount, for example, but you can't change
.B gid
or
.B umask
for the
.IR fatfs ).
.PP
It is possible that the files
.I /etc/mtab
and
.I /proc/mounts
don't match on systems with a regular
.I mtab
file.  The first file is based only on
the mount command options, but the content of the second file also depends on
the kernel and others settings (e.g.\& on a remote NFS server -- in certain cases
the mount command may report unreliable information about an NFS mount point
and the
.I /proc/mount
file usually contains more reliable information.)  This is
another reason to replace the
.I mtab
file with a symlink to the
.I /proc/mounts
file.
.PP
Checking files on NFS filesystems referenced by file descriptors (i.e.\& the
.B fcntl
and
.B ioctl
families of functions) may lead to inconsistent results due to the lack of
a consistency check in the kernel even if the
.B noac
mount option is used.
.PP
The
.B loop
option with the
.B offset
or
.B sizelimit
options used may fail when using older kernels if the
.B mount
command can't confirm that the size of the block device has been configured
as requested.  This situation can be worked around by using
the
.B losetup
command manually before calling
.B mount
with the configured loop device.
.SH AUTHORS
.nf
Karel Zak <kzak@redhat.com>
.fi
.SH SEE ALSO
.na
.BR lsblk (1),
.BR mount (2),
.BR umount (2),
.BR filesystems (5),
.BR fstab (5),
.BR nfs (5),
.BR xfs (5),
.BR mount_namespaces (7)
.BR xattr (7)
.BR e2label (8),
.BR findmnt (8),
.BR losetup (8),
.BR mke2fs (8),
.BR mountd (8),
.BR nfsd (8),
.BR swapon (8),
.BR tune2fs (8),
.BR umount (8),
.BR xfs_admin (8)
.ad
.SH AVAILABILITY
The mount command is part of the util-linux package and is available from
https://www.kernel.org/pub/linux/utils/util-linux/.