This guide provides information about how to manage storage devices on a SUSE Linux Enterprise Server.
- Preface
- I File systems and mounting
- II Logical volumes (LVM)
- 5 LVM configuration
- 5.1 Understanding the logical volume manager
- 5.2 Creating volume groups
- 5.3 Creating logical volumes
- 5.4 Automatically activating non-root LVM volume groups
- 5.5 Resizing an existing volume group
- 5.6 Resizing a logical volume
- 5.7 Deleting a volume group or a logical volume
- 5.8 Disabling LVM on boot
- 5.9 Using LVM commands
- 5.10 Tagging LVM2 storage objects
- 6 LVM volume snapshots
- 5 LVM configuration
- III Software RAID
- IV Network storage
- 14 iSNS for Linux
- 15 Mass storage over IP networks: iSCSI
- 15.1 Installing the iSCSI LIO target server and iSCSI initiator
- 15.2 Setting up an iSCSI LIO target server
- 15.3 Configuring iSCSI initiator
- 15.4 Setting up software targets using targetcli-fb
- 15.5 Using iSCSI disks when installing
- 15.6 Troubleshooting iSCSI
- 15.7 iSCSI LIO target terminology
- 15.8 More information
- 16 Fibre Channel storage over Ethernet networks: FCoE
- 17 NVMe-oF
- 18 Managing multipath I/O for devices
- 18.1 Understanding multipath I/O
- 18.2 Hardware support
- 18.3 Planning for multipathing
- 18.4 Installing SUSE Linux Enterprise Server on multipath systems
- 18.5 Updating SLE on multipath systems
- 18.6 Multipath management tools
- 18.7 Configuring the system for multipathing
- 18.8 Multipath configuration
- 18.9 Configuring policies for failover, queuing, and failback
- 18.10 Configuring path grouping and priorities
- 18.11 Selecting devices for multipathing
- 18.12 Multipath device names and WWIDs
- 18.13 Miscellaneous options
- 18.14 Best practice
- 18.15 Troubleshooting MPIO
- 19 Sharing file systems with NFS
- 20 Samba
- 21 On-demand mounting with autofs
- A GNU licenses
- 1.1 Enabling Btrfs quotas
- 1.2 Setting quota for a subvolume
- 1.3 List of subvolumes for a device
- 5.1 Physical partitioning versus LVM
- 5.2 Physical volumes in the volume group named DATA
- 7.1 Example RAID 5 configuration
- 14.1 iSNS discovery domains
- 15.1 iSCSI SAN with an iSNS server
- 16.1 Open Fibre channel over ethernet SAN
- 19.1 NFS server configuration tool
- 20.1 Determining Windows domain membership
- 20.2 Windows Explorer dialog
- 20.3 Windows Explorer directory listing with compressed files
- 20.4 Adding a new Samba share with snapshots enabled
- 20.5 The tab in Windows explorer
- 1.1 File system types in Linux
- 1.2 Maximum sizes of files and file systems (on-disk format, 4 KiB block size)
- 1.3 Storage limitations
- 2.1 File system support for resizing
- 7.1 Comparison of RAID 5 and RAID 6
- 9.1 Nested RAID levels
- 9.2 Scenario for creating a RAID 10 (1+0) by nesting
- 9.3 Scenario for creating a RAID 10 (0+1) by nesting
- 9.4 Complex RAID 10 compared to nested RAID 10
- 9.5 Scenario for creating a RAID 10 using mdadm
- 11.1 Tasks involved in resizing a RAID
- 11.2 Scenario for increasing the size of component partitions
- 12.1 Translation between non-SES-2 patterns and SES-2 patterns
Copyright © 2006–2024 SUSE LLC und Mitwirkende. Alle Rechte vorbehalten.
Es wird die Genehmigung erteilt, dieses Dokument unter den Bedingungen der GNU Free Documentation License, Version 1.2 oder (optional) Version 1.3 zu vervielfältigen, zu verbreiten und/oder zu verändern; die unveränderlichen Abschnitte hierbei sind der Urheberrechtshinweis und die Lizenzbedingungen. Eine Kopie dieser Lizenz (Version 1.2) finden Sie im Abschnitt “GNU Free Documentation License”.
Die SUSE-Marken finden Sie unter https://www.suse.com/company/legal/. Alle anderen Marken von Drittanbietern sind Besitz ihrer jeweiligen Eigentümer. Markensymbole (®, ™ usw.) kennzeichnen Marken von SUSE und der Tochtergesellschaften. Sternchen (*) kennzeichnen Marken von Drittanbietern.
Alle Informationen in diesem Buch wurden mit größter Sorgfalt zusammengestellt. Doch auch dadurch kann hundertprozentige Richtigkeit nicht gewährleistet werden. Weder SUSE LLC noch ihre Tochtergesellschaften noch die Autoren noch die Übersetzer können für mögliche Fehler und deren Folgen haftbar gemacht werden.