| Next revision | Previous revision Next revisionBoth sides next revision |
| zh-cn:doc:howto:storage [2015/06/10 11:19] – created yangfl | zh-cn:doc:howto:storage [2018/02/25 15:05] – ↷ Links adapted because of a move operation |
|---|
| | ====== 分区、格式化及安装存储设备 ====== |
| | 请参见[[docs:techref:flash.layout]]。 |
| |
| | |
| | 向OpenWrt系统添加存储设备是一个非常有价值的选项,因为嵌入式设备上的闪存容量通常很有限。Having ample storage for applications and other data can therefore greatly expand OpenWrt functionality. For example you can turn your device into a full [[wp>NAS]] by adding a hard drive for storing media files. You can also add storage to increase the available storage for the root file system in an overlay configuration by employing [[docs:user-guide:additional-software:extroot_configuration]]. |
| | |
| | Before the system can find your device it has to be properly recognised, which is done by installing the correct drivers for the device. For most devices the connection will be through USB, so you first have to install [[usb.essentials|USB support]] and then provide [[usb.storage|storage support over USB]]. Other devices are possible too, like SATA, IDE and flash memory cards, see [[doc:howto:sata.essentials]], [[doc:howto:ide.essentials]] and [[doc:howto:cf.essentials]], respectively. This article will assume that your storage device is already installed correctly with the correct drivers and ready for use. |
| | |
| | After installing the drivers for a device it can be [[disk.encryption|encrypted]] (optional) then has to be [[wp>Disk partitioning|partitioned]] and [[wp>Disk formatting|formatted]] with a [[wp>File system]] (e.g. [[wp>ext4]], [[wp>File Allocation Table|FAT]]) before data can be addressed as [[wp>Computer file|files]] and [[wp>mount (computer)|mounted]] by the OS. The usual Linux tools can be used to achieve these tasks from within OpenWrt. Certain packages are necessary for specific file system support and other packages facilitate more advanced functionality. This article explains the specifics and caveats of working with storage devices in OpenWrt and provides examples. |
| | |
| | ===== 分区 ===== |
| | |
| | Partitioning means to write a partition table to the device, which defines which parts of the available space on the device belongs to which partition, each of which can have its own file system. Most commonly used partition tables are the [[wp>Master Boot Record]] (MBR) and the [[wp>GUID Partition Table]] (GPT). The latter is more modern and supports larger disks and more partitions. A device can also be used without a partition table, in which case there is only one file system on the device. |
| | |
| | You can partition your device before connecting it to your OpenWrt powered device (e.g. on a PC), which may provide a wider range of options, like GPT support. You can then also format any partitions before attaching your device. However, there are packages in the OpenWrt repositories with which you can partition your devices: |
| | |
| | ***''fdisk''** is the standard tool to partition drives in Linux. //for help with **partitioning** see [[http://www.tldp.org/HOWTO/Partition/fdisk_partitioning.html|TLDP]]//) |
| | ***''cfdisk''** is a curses-based program for partitioning drives. Similar to fdisk, but provides a convenient menu based interface. |
| | ***''sfdisk''** is an alternative to list the size of a partition, list the partitions on a device, check the partitions on a device and repartition a device. |
| | |
| | | {{:meta:icons:tango:48px-emblem-important.svg.png?nolink}} | All these utilities support MBR based partition tables only. Currently there are no tools in the default OPKG repository to create and partition GPT based devices. The Linux tools ''parted'' and ''gdisk'' have not yet been included. Note that while it cannot create GPT tables, there is full support for GPT disks in the OpenWrt kernel, so prepartitioned drives with GPT will work. Also note that if you want to erase a GPT partition table and clear the device to start over with a MBR partition table you have to delete the backup copies of the table that GPT defines, usually also at the end of the device. Since there is no true GPT tool for this in the repository yet, you can erase the tables with the ''dd'' tool. This is a [[https://github.com/tobiaswaldvogel/openwrt-addpack/blob/master/parted/Makefile| parted makefile]] for OpenWrt that someone provides. After adding dependencies for libblkid and libuuid the package builds fine. Maybe someone should send a patch to the devel-mailinglist.| |
| | |
| | Upon having your device partitioned, its partitions should be available as '[[wp>Device file]]s' under ''/dev/''. For example ''/dev/sda'' as the device, with ''/dev/sda1'', ''/dev/sda2'', ... , the partitions. Or, in case it is not partitioned with a partition table and it has a single file system, it may be directly accessible under e.g. ''/dev/sda''. Subsequent devices you add will be ''/dev/sdb'', ''/dev/sdc'' and so on. These 'device files' can now be formatted (see below). |
| | |
| | :!: Windows只能检测出可移动驱动器上的*一个*分区。 |
| | |
| | ===== 格式化文件系统 ===== |
| | |
| | Available file systems and their packages can be listed with ''opkg update; opkg list "kmod-fs*"''. These are kernel packages that provide necessary kernel support for reading and writing these file systems. The following table lists these file system kernel packages. |
| | |
| | ^ 名称 ^ 描述 ^ |
| | | kmod-fs-autofs4 | AutoFS支持内核模块 | |
| | | kmod-fs-btrfs | [[wp>zh:Btrfs|Btrfs]]支持内核模块 | |
| | | kmod-fs-cifs | CIFS支持内核模块 | |
| | | kmod-fs-exportfs | exportfs内核模块。需要配合其他一些模块。 | |
| | | kmod-fs-ext4 | [[wp>zh:ext2|ext2]]、[[wp>zh:ext3|ext3]]及[[wp>zh:ext4|ext4]]文件系统支持内核模块(但在Backfire上ext2或ext3分区都必须挂载为ext4分区,参见疑难解答。)| |
| | | kmod-fs-hfs | HFS文件系统支持内核模块 | |
| | | kmod-fs-hfsplus | HFS+文件系统支持内核模块 | |
| | | kmod-fs-isofs | ISO9660文件系统支持内核模块 | |
| | | kmod-fs-minix | [[wp>zh:MINIX文件系统|MINIX文件系统]]支持内核模块 | |
| | | kmod-fs-msdos | MSDOS文件系统支持内核模块 | |
| | | kmod-fs-nfs | NFS支持内核模块 | |
| | | kmod-fs-nfs-common | 通用NFS文件系统模块 | |
| | | kmod-fs-nfsd | NFS内核服务器支持内核模块 | |
| | | kmod-fs-ntfs | NTFS__只读__文件系统支持内核模块 | |
| | | kmod-fs-reiserfs | [[wp>zh:ReiserFS|ReiserFS]]支持内核模块 | |
| | | kmod-fs-udf | [[wp>zh:UDF|UDF]]文件系统支持内核模块 | |
| | | kmod-fs-vfat | VFAT文件系统支持内核模块 | |
| | | kmod-fs-xfs | [[wp>zh:XFS|XFS]]支持内核模块 | |
| | |
| | The choice of file system is dependent on several factors: performance, compatibility with other systems, functionality such as compression and journaling, security, etc. The remarks below are important to keep in mind when choosing your file system. |
| | |
| | |
| | [[https://forum.openwrt.org/viewtopic.php?id=27750|OpenWrt-Forum: Benchmarks with different filesystems]] |
| | |
| | |
| | | <HTML><font size="6"; color="green">✔</font> </HTML> | 推荐使用**[[wp>zh:ext2|ext2]]**、**[[wp>zh:ext3|ext3]]**或**[[wp>zh:ext4|ext4]]**文件系统(都受**kmod-fs-ext4**支持)[有时kmod-fs-ext4只支持ext4!] | |
| | | {{:meta:icons:tango:48px-outdated.svg.png?nolink}} | 截至[[https://dev.openwrt.org/changeset/26645|r26645]] the //modules// for ext2 and ext3 (kmod-fs-ext2 and kmod-fs-ext3) are no longer available. You can use the module for ext4 **kmod-fs-ext4** to mount ext2/ext3 as well, but then you have to mount your ext2 or ext3 partition like ext4 partition: ''mount -t ext4 /dev/sda1 /mnt/share -o rw,sync'' | |
| | | {{:meta:icons:tango:dialog-information.png?nolink}} | If you are planning on sharing your USB storage with Samba, and/or using it to share large multimedia content over UPnP, e.g. with ushare, you should use ext3 or ext4 rather than ext2. Default Ext2 partitions will be limited to files of no more than 4 Gb, but this restriction is eliminated with the newer filesystems. To retain good performance with the newer filesystems, particularly on flash USB storage, you should also consider disabling journaling with the "''-O ^has_journal''" when using ''mkfs.ext4'' to format the filesystem. Also for ext4, the "extent" formatting option (e.g. "''-O ^has_journal,extent''") will make filesystem access to large files more performant. | |
| | | {{:meta:icons:tango:dialog-information.png?nolink}} | With [[wp>Ext2Fsd]] you obtain read/write access to ext2 ext3 and ext4 filesystems in Microsoft Windows. Native Linux file systems like ext2 or ext3 are the first choice when working with Linux. Don't bother with NTFS, VFAT and the like. They all have some quirks we could do without. | |
| | | <HTML><font size="6"; color="red">✘</font> </HTML> | We do **NOT** recommend using [[wp>NTFS]]. While it is possible, it has serious performance issues under Linux.\\ If, for whatever reasons, you insist to utilize NTFS as file system, you may find [[writable_ntfs|Writable NTFS]] helpful. | |
| | |
| | |
| | |
| | ==== 可用NLS文件 ==== |
| | |
| | For some filesystems, like for VFAT, you need to additionally install language packages (codepages / charsets) to handle the filenames. If your mount fails, look in dmesg - a message like |
| | |
| | ''FAT: codepage cp437 not found'' |
| | |
| | 表示需要NLS代码页437,而这个消息 |
| | |
| | ''FAT: IO charset iso8859-1 not found'' |
| | |
| | 表示需要NLS ISO 8859-1。 |
| | |
| | ***''kmod-nls-base''** Kernel module for NLS (Native Language Support) |
| | |
| | Available NLS files and their packages can be listed with ''opkg update; opkg list "kmod-nls*"''. |
| | |
| | ^ 名称 ^ 描述 ^ |
| | | kmod-nls-cp1250 | Kernel module for NLS Codepage 1250 (Eastern Europe) | |
| | | kmod-nls-cp1251 | Kernel module for NLS Codepage 1251 (Russian) | |
| | | kmod-nls-cp437 | Kernel module for NLS Codepage 437 (United States, Canada) | |
| | | kmod-nls-cp775 | Kernel module for NLS Codepage 775 (Baltic Rim) | |
| | | kmod-nls-cp850 | Kernel module for NLS Codepage 850 (Europe) | |
| | | kmod-nls-cp852 | Kernel module for NLS Codepage 852 (Europe) | |
| | | kmod-nls-cp866 | Kernel module for NLS Codepage 866 (Cyrillic) | |
| | | kmod-nls-iso8859-1 | Kernel module for NLS ISO 8859-1 (Latin 1) | |
| | | kmod-nls-iso8859-13 | Kernel module for NLS ISO 8859-13 (Latin 7; Baltic) | |
| | | kmod-nls-iso8859-15 | Kernel module for NLS ISO 8859-15 (Latin 9) | |
| | | kmod-nls-iso8859-2 | Kernel module for NLS ISO 8859-2 (Latin 2) | |
| | | kmod-nls-koi8r | Kernel module for NLS KOI8-R (Russian) | |
| | | kmod-nls-utf8 | Kernel module for NLS UTF-8 | |
| | |
| | ==== Formatting and File System Checking from within OpenWrt ==== |
| | The package [[wp>E2fsprogs|e2fsprogs]] contains the essential ext2/3/4 filesystem utilities ''e2fsck'', ''mke2fs'', ''debugfs'', ''dumpe2fs'' and ''tune2fs'', and also most of the other core ext2/3/4 filesystem utilities available. For help with **formatting** see [[http://www.tldp.org/HOWTO/Partition/formatting.html|TLDP]]. Also see [[http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/e2fsprogs.html|this page]] and [[http://e2fsprogs.sourceforge.net/|the official page]] for more information on e2fsprogs. |
| | |
| | === 示例 === |
| | As an example, for a device situated at ''/dev/sda'', to format its second partition ''/dev/sda2'' with the ext4 file system you can run |
| | mkfs.ext4 /dev/sda2 |
| | |
| | :!: **Note:** When doing this, there will be no warning before execution and a new empty ext4 file system will be written to ''/dev/sda2'' immediately, using a quick format. Any data on the partition cannot be easily retrieved or is lost. Make sure that you enter the correct device file and partition as an argument for the formatting tool. |
| | |
| | === File System Checking === |
| | The file system checking utilities can be used in case the file system requires checking for errors. |
| | |
| | :!: **Note:** In order to perform a ''e2fsck'' on 1 GiB partition, you will need at least 1 MiB of RAM.(([[http://www.openbsd.org/faq/faq14.html#LargeDrive|Source]].)) The same is true for ''mke2fs''. You can solve this by mounting a SWAP partition (or by using a device with enough RAM). |
| | |
| | :!: **Note:** In order to do ''fsck'' (aka CHKDSK) of FAT32/VFAT partitions before mounting (i.e. during the boot process), you should read the following tickets: |
| | [[https://dev.openwrt.org/ticket/10714|Incorrect log output for mount point file systems without a fsck]], and |
| | [[https://dev.openwrt.org/ticket/10697|Missing fsck function for block-mount/-hotplug of dos/vfat filesystems]] |
| | |
| | |
| | ===== Automatic Mount on Boot ===== |
| | |
| | :!: see [[docs:techref:block_mount]] |
| | |
| | It is convenient to be able to mount your file systems on boot. The package ''block-mount'' will take care of this and also enable automatic mount when device is plugged in through use of [[docs:techref:ubox|ubox]]. As is typical in Linux, this is handled with [[docs:user-guide:storage:fstab|Fstab Configuration]]. OpenWrt provides [[docs:user-guide:base-system:uci|UCI]] configuration of Fstab. The configuration file is ''[[docs:user-guide:storage:fstab|/etc/config/fstab]]''. |
| | |
| | For a technical background in which Fstab works, see [[docs:techref:block_mount]]. Note the information box below mentioning the new block-mount packages which works in conjunction with ubox. |
| | |
| | Example settings in ''fstab'' for mounting to ''/mnt/share'' with automatic detection of the file system: |
| | | '' |
| | config 'mount' |
| | option 'device' '/dev/sda1' |
| | option 'options' 'rw,sync' |
| | option 'enabled_fsck' '0' |
| | option 'enabled' '1' |
| | option 'target' '/mnt/share' |
| | '' | |
| | |
| | And to make the fstab settings effective in current session run: |
| | <code>/etc/init.d/fstab start</code> |
| | |
| | To make the fstab settings effective after every reboot run: |
| | <code>/etc/init.d/fstab enable</code> |
| | |
| | :!: **Note:** If you are having trouble with fstab, see [[docs:user-guide:storage:fstab#troubleshooting|fstab troubleshooting]]. |
| | |
| | UCI CLI commands: |
| | <code> |
| | /etc/init.d/fstab stop |
| | uci add fstab mount |
| | uci set fstab.@mount[-1].device=/dev/sda1 |
| | uci set fstab.@mount[-1].options=rw,sync |
| | uci set fstab.@mount[-1].enabled_fsck=0 |
| | uci set fstab.@mount[-1].enabled=1 |
| | uci set fstab.@mount[-1].target=/mnt/share |
| | uci commit fstab |
| | /etc/init.d/fstab start |
| | </code> |
| | |
| | Delete with UCI CLI commands: |
| | <code>/etc/init.d/fstab stop |
| | uci delete fstab.@mount[0] |
| | uci commit fstab |
| | /etc/init.d/fstab start</code> |
| | |
| | |
| | | {{:meta:icons:tango:48px-outdated.svg.png?nolink}} | In [[https://dev.openwrt.org/changeset/26314/trunk|r26314]] the three opkg packages ''block-mount'', ''block-extroot'' and ''block-hotplug'' have been merged into **''block-mount''**. | |
| | | {{:meta:icons:tango:48px-outdated.svg.png?nolink}} | In [[https://dev.openwrt.org/changeset/36988|r36988]] **''[[docs:techref:ubox]]''** is a dependency of the opkg package ''block-mount''. block-mount now contains the executable ''block''. ''block <info|mount|umount|detect>'' | |
| | | {{:meta:icons:tango:48px-emblem-important.svg.png?nolink}} | **[[https://lists.openwrt.org/pipermail/openwrt-devel/2013-July/020591.html|2013-07-04: new block mount howto]]** | |
| | |
| | ===== Mounting ===== |
| | |
| | There is no additional configuration needed for mounting your file system when the device is properly configured. Mounting works as is typical in Linux. Read the manual page for [[http://linux.die.net/man/8/mount|mount]]. Pay special attention to the options. |
| | |
| | You can only mount a partition to an existing directory. You can create it with [[http://linux.die.net/man/1/mkdir|mkdir]], for example: |
| | <code> |
| | mkdir -p /mnt/shares |
| | </code> |
| | |
| | To manually mount a partition, assuming that the second partition ''/dev/sda2'' on the device ''/dev/sda'' is formatted with an ext4 file system, use: |
| | <code> |
| | mount -t ext4 /dev/sda2 /mnt/shares |
| | </code> |
| | |
| | The device can now be accessed at ''/mnt/shares''. Note that the ''-t ext4'' option is not strictly necessary as the file system is usually automatically detected. |
| | |
| | To check if mounting was successful use ''df'': |
| | <code> |
| | root@OpenWrt:~# df -h |
| | Filesystem Size Used Available Use% Mounted on |
| | rootfs 28.8M 4.5M 24.3M 16% / |
| | /dev/root 2.0M 2.0M 0 100% /rom |
| | tmpfs 61.8M 400.0K 61.4M 1% /tmp |
| | /dev/mtdblock5 28.8M 4.5M 24.3M 16% /overlay |
| | overlayfs:/overlay 28.8M 4.5M 24.3M 16% / |
| | tmpfs 512.0K 0 512.0K 0% /dev |
| | /dev/sda2 18.7G 67.6M 13.9G 0% /mnt/shares |
| | </code> |
| | The device is listed here with its mount point in the last line. You can also run ''mount'' without arguments to list all mount points. |
| | |
| | To unmount: |
| | umount /mnt/shares |
| | |
| | To mount a [[wp>Paging|swap]] partition, assuming that the first partition on the ''/dev/sda'' device is linux swap space: |
| | swapon /dev/sda1 |
| | |
| | In case ''/dev/sda1'' is not swap space yet, you can run |
| | mkswap /dev/sda1 |
| | |
| | You can check swap functionality and status with the ''free'' command. You can also check its status using ''top'' or ''htop'' (installable package). |
| | |
| | To unmount a swap partition: |
| | swapoff /dev/sda1 |
| | |
| | |
| | Usually the devices that you use are [[wp>Device_file#Block_devices|block devices]]. In OpenWrt, extra utilities for block devices such as automatic mounting are provided with a collection of tools for [[docs:techref:block_mount|block devices]], see also below. |
| | |
| | |
| | ===== Advanced Topics ===== |
| | |
| | * Use [[extroot]]. This will allow you to use your device as a root, by using it in an overlay configuration over the original root. |
| | |
| | * Once you successfully mounted your partition, you may want to install packages onto it. Please see [[docs:user-guide:additional-software:opkg#Installation.Destination]] for that. |
| | |
| | * :!: Do not install kernel modules on USB, see [[https://dev.openwrt.org/ticket/10739]] |
| | |
| | ==== Automatic spin down an attached hard disk ==== |
| | If you have attached an external hard disk (e.g. through the USB port) and you don't use the disk all the time, you may want to spin down the disk after some time. One possible reason for this is to reduce the noise. A second reason is that some fanless external racks can get very hot and this is not healthy for the disk. |
| | |
| | Unfortunately there is no solution that works always for everybody. The first option to try is provided by the package [[http://hd-idle.sourceforge.net/|''hd-idle'']], which will spin down any disk accessible via the SCSI layer. Install it and test if it can spindown the hard disk (let us assume that your disk is ''/dev/sda''): |
| | <code> |
| | opkg install hd-idle |
| | hd-idle -t sda |
| | </code> |
| | If you can hear the disk spins down, then you can configure the package, the configuration is in ''/etc/config/hd-idle''. |
| | |
| | If ''hd-idle'' doesn't work, then the next option to try is hdparm: |
| | |
| | <code> |
| | opkg install hdparm |
| | hdparm -y /dev/sda |
| | </code> |
| | |
| | If you hear the disk spins down, then create a script ''/etc/spindown'' with the following contents: |
| | <code> |
| | #!/bin/sh |
| | |
| | oldstate='' |
| | n="$2" |
| | while :; do |
| | sleep 60 |
| | newstate=$(grep "$1" /proc/diskstats) |
| | if [ "$newstate" = "$oldstate" ]; then |
| | n=$(($n - 1)) |
| | [ "$n" != 0 ] || hdparm -y /dev/"$1" |
| | else |
| | n="$2" |
| | oldstate=$newstate |
| | fi |
| | done & |
| | </code> |
| | Then add to ''/etc/rc.local'' the following command (assuming your disk is ''/dev/sda'' and you want to spin it down after 20 minutes of inactivity): |
| | <code> |
| | /etc/spindown sda 20 |
| | </code> |
| | A much easier way is this: if the above command ''hdparm -y /dev/sda'' works, insert the following command to ''/etc/rc.local'': |
| | <code> |
| | hdparm -S 240 /dev/hda |
| | </code> |
| | The setting ''240'' equals 20 mins, the time coding can be checked on the [[http://unixhelp.ed.ac.uk/CGI/man-cgi?hdparm|''hdparm man page'']]. |
| | |
| | The third option to try is the package ''sdparm'': |
| | <code> |
| | opkg install sdparm |
| | sdparm -f -C stop /dev/sda |
| | </code> |
| | If you hear the disk spins down, use the script ''/etc/spindown'' as in the case of hdparm, however replace the line |
| | <code> |
| | [ "$n" != 0 ] || hdparm -y /dev/"$1" |
| | </code> |
| | with the line |
| | <code> |
| | [ "$n" != 0 ] || sdparm -f -C stop /dev/"$1" |
| | </code> |
| | |
| | ===== Virtual Disk ===== |
| | Now let's do a virtual disk. You need an additional package. |
| | |
| | <code> |
| | opkg update |
| | opkg install kmod-fs-ext3 kmod-loop e2fsprogs |
| | insmod ext3 |
| | insmod loop |
| | </code> |
| | |
| | Then, create, and format the disk:\\ |
| | |
| | <code> |
| | dd if=/dev/zero of=/mnt/hdd/owrt_loop bs=1M count=128 |
| | mke2fs -j -F -b 1024 /mnt/hdd/owrt_loop |
| | </code> |
| | |
| | To be able to use, plug-in for OpenWrt:\\ |
| | |
| | <code> |
| | mkdir /mnt/loopdisk |
| | mount -o loop /mnt/hdd/owrt_loop /mnt/loopdisk |
| | </code> |
| | |
| | Now our system is not only the OpenWrt xMB, but x+128 MB\\ |
| | |
| | If you want to install packages into this virtual disk, see: |
| | [[docs:user-guide:additional-software:opkg#installation_destinations|opkg installation destinations]] |
| | |
| | ===== Troubleshooting ===== |
| | |
| | ==== I have problems with FAT or NTFS file systems ==== |
| | There are numerous things that go wrong with file systems not made for Linux. ext2, ext3 or ext4 file systems are therefore preferred. |
| | |
| | ==== kmod-fs-ext4 won't mount ext2 or ext3 partition ==== |
| | |
| | **Symptoms**: You are trying to mount **ext2** or **ext3** partition and you have installed only **kmod-fs-ext4**. Neither ''mount'' command nor ''fstab'' works. The kmod-fs-ext4 issue definitely applies to Backfire, but is not an issue for Attitude Adjustment (tested on Attitude Adjustment RC1). |
| | |
| | **Solution a)**: you have to make sure that you are trying to mount the ext2 or ext3 partition like it was ext4 partition. Example [[docs:user-guide:storage:fstab|/etc/config/fstab]] config and mount command follows: |
| | |
| | |''config mount |
| | option target /mnt |
| | option device /dev/sda1 # sda1 is ext3 partition |
| | option fstype **ext4** # but is mounted as ext4, since we have installed kmod-fs-ext4 only |
| | option options rw,sync |
| | option enabled 1 |
| | option enabled_fsck 1 |
| | ''| |
| | |
| | <code>mount -t ext4 /dev/sda1 /mnt -o rw,sync</code> |
| | |
| | **Solution b)**: install ''kmod-fs-ext3'' or ''kmod-fs-ext2'' filesystem. |
| | |
| | <code> |
| | opkg update |
| | opkg install kmod-fs-ext3 |
| | </code> |
| | |
| | :!: This only applies to Backfire |
| | |
| | **Solution c)**: just set ext4 on usb/drive etc. |
| | |
| | :!: This problem occured for me in ATTITUDE ADJUSTMENT (12.09, r36088) when I had problem with mount ext3 with kmod-fs-ext4 (in addition I had also problem with install kmod-fs-ext3). |
| | |
| | |
| | ===== Other Useful Packages ===== |
| | |
| | ***''swap-utils''** This package contains a collection of tools for managing swap space: ''mkswap'', ''swapon'' and ''swapoff''. FIXME This package exists, but swapon and swapoff seem to be just built into Busybox. Can someone explain this here? |
| | ***''blkid''** Command-line utility to locate/print block device attributes. |
| | ***''dd''** A bit-stream duplicator to write directly to block devices. |
| | |
| | ===== Filesystems not in OpenWrt ===== |
| | |
| | * exFAT: [[https://forum.openwrt.org/viewtopic.php?id=45293|forum thread]] |
| | * f2fs: [[https://forum.openwrt.org/viewtopic.php?id=48805]] |
| | |
| | ===== Notes ===== |
| | :!: **Note:** If you are having trouble using storage on a Huawei 3G dongle, you should read the following ticket:[[https://dev.openwrt.org/ticket/10716|Mass storage missing from 3G dongle]] |