| /external/e2fsprogs/tests/f_badjourblks/ |
| expect.1 | 4 *** ext3 journal has been deleted - filesystem is now ext2 only ***
22 Recreate journal to make the filesystem ext3 again?
27 *** journal has been re-created - filesystem is now ext3 again ***
|
| /external/e2fsprogs/tests/f_miss_journal/ |
| expect.1 | 4 *** ext3 journal has been deleted - filesystem is now ext2 only ***
20 Recreate journal to make the filesystem ext3 again?
25 *** journal has been re-created - filesystem is now ext3 again ***
|
| /external/e2fsprogs/tests/f_crashdisk/ |
| expect.1 | 5 filesystem. If the device is valid and it really contains an ext2
6 filesystem (and not swap or ufs or something else), then the superblock
|
| /external/e2fsprogs/misc/ |
| mke2fs.conf.5.in | 77 filesystem types. The filesystem type can be specified explicitly using
82 If no filesystem type is specified,
84 will use the filesystem type
86 if the filesystem size is less than or equal to 3 megabytes.
87 If the filesystem size is greater than 3 but less than or equal to
90 will use the filesystem
94 will use the default filesystem type
105 relation found in the filesystem-type-specific subsection of
114 relation. It may be overridden by the filesystem-specific
[all...] |
| mklost+found.8.in | 18 directory in the root directory of each filesystem.
25 is being run to recover a filesystem, it does not need to allocate blocks in
26 the filesystem to store a large number of unlinked files. This ensures that
28 will not have to allocate data blocks in the filesystem during recovery.
|
| mke2fs.8.in | 7 mke2fs \- create an ext2/ext3 filesystem
92 .I filesystem-type
131 is used to create an ext2/ext3 filesystem (usually in a disk partition).
150 the expected usage of the filesystem (see the
169 Set extended options for the filesystem. Extended options are comma
183 Configure the filesystem for a RAID array with
185 filesystem blocks. This is the number of blocks read or written to disk
186 before moving to next disk. This mostly affects placement of filesystem
193 Configure the filesystem for a RAID array with
195 filesystem blocks per stripe. This is typically be stride-size * N, wher
[all...] |
| e2image.8.in | 7 e2image \- Save critical ext2/ext3 filesystem metadata to a file
18 program will save critical ext2 or ext3 filesystem metadata located on
31 recover a badly damaged filesystem.
53 The image file should be stored on some filesystem other than
54 the filesystem whose data it contains, to ensure that this data is
55 accessible in the case where the filesystem has been badly damaged.
69 filesystem, with 200,000 inodes in use out of 1.2 million inodes, the
70 image file will be approximately 35 megabytes; a 4 gigabyte filesystem with
76 .SH RESTORING FILESYSTEM METADATA USING AN IMAGE FILE
81 file back to the device. It can be used to restore the filesystem metadat
[all...] |
| /external/e2fsprogs/debian/attic/ |
| e2fslibsg-dev.menu | 3 longtitle="A library to handle low-level structures in an ext2 filesystem"\
|
| /external/e2fsprogs/debian/ |
| e2fslibs-dev.doc-base | 5 user-level programs to manipulate an ext2 filesystem.
|
| /external/e2fsprogs/tests/f_badjour_indblks/ |
| expect.1 | 4 *** ext3 journal has been deleted - filesystem is now ext2 only ***
6 Adding dirhash hint to filesystem.
24 Recreate journal to make the filesystem ext3 again?
29 *** journal has been re-created - filesystem is now ext3 again ***
|
| /external/e2fsprogs/debugfs/ |
| debug_cmds.ct | 10 request do_open_filesys, "Open a filesystem",
13 request do_close_filesys, "Close the filesystem",
19 request do_dirty_filesys, "Mark the filesystem as dirty",
22 request do_init_filesys, "Initalize a filesystem (DESTROYS DATA)",
109 request do_write, "Copy a file from your native filesystem",
118 request do_lcd, "Change the current directory on your native filesystem",
121 request do_rdump, "Recursively dump a directory to the native filesystem",
|
| /external/kernel-headers/original/linux/ |
| efs_fs_sb.h | 26 __be32 fs_size; /* size of filesystem, in sectors */
32 __be16 fs_ncg; /* # of cylinder groups in filesystem */
51 __u32 fs_start; /* first block of filesystem */
52 __u32 first_block; /* first data block in filesystem */
53 __u32 total_blocks; /* total number of blocks in filesystem */
|
| /external/e2fsprogs/tests/r_inline_xattr/ |
| expect | 8 Resizing the filesystem on ./test.img to 5120 (1k) blocks.
9 The filesystem on ./test.img is now 5120 blocks long.
|
| /system/core/rootdir/etc/ |
| dbus.conf | 12 means use abstract namespace, don't really create filesystem
17 <!-- Allow everything, D-Bus socket is protected by unix filesystem
|
| /external/e2fsprogs/lib/ext2fs/ |
| sparse.c | 2 * sparse.c --- find the groups in an ext2 filesystem with metadata backups
46 * ext3 filesystem. The counters should be initialized to 1, 5, and 7 before
47 * calling this for the first time. In a sparse filesystem it will be the
49 * For a non-sparse filesystem it will be every group: 1, 2, 3, 4, ...
|
| ext2_err.c | 29 "Filesystem revision too high",
30 "Attempt to write to filesystem opened read-only",
43 "Filesystem has unexpected block size",
45 "Attempt to read block from filesystem resulted in short read",
46 "Attempt to write block from filesystem resulted in short write",
53 "Not enough space to build proposed filesystem",
76 "Filesystem has unsupported feature(s)",
77 "Filesystem has unsupported read-only feature(s)",
81 "Could not allocate block in ext2 filesystem",
82 "Could not allocate inode in ext2 filesystem",
[all...] |
| ext2_err.et.in | 72 "Filesystem revision too high"
75 "Attempt to write to filesystem opened read-only"
114 "Filesystem has unexpected block size"
120 "Attempt to read block from filesystem resulted in short read"
123 "Attempt to write block from filesystem resulted in short write"
144 "Not enough space to build proposed filesystem"
213 "Filesystem has unsupported feature(s)"
216 "Filesystem has unsupported read-only feature(s)"
228 "Could not allocate block in ext2 filesystem"
231 "Could not allocate inode in ext2 filesystem"
[all...] |
| /external/e2fsprogs/tests/f_dirlink/ |
| expect.1 | 0 Filesystem did not have a UUID; generating one.
|
| /external/e2fsprogs/tests/f_okgroup/ |
| expect.1 | 0 Filesystem did not have a UUID; generating one.
|
| /external/genext2fs/ |
| README | 1 genext2fs generates an ext2 filesystem as a normal (non-root) user.
|
| /external/yaffs2/yaffs2/ |
| Makefile | 2 # Makefile for the linux YAFFS filesystem routines.
|
| /cts/tests/tests/net/src/android/net/cts/ |
| LocalSocketAddress_NamespaceTest.java | 37 assertEquals(Namespace.FILESYSTEM, Namespace.valueOf("FILESYSTEM"));
50 assertEquals(Namespace.FILESYSTEM, expected[2]);
|
| /external/e2fsprogs/tests/f_badprimary/ |
| expect.1 | 0 Filesystem did not have a UUID; generating one.
6 If the block is really bad, the filesystem can not be fixed.
14 If the block is really bad, the filesystem can not be fixed.
|
| /external/e2fsprogs/e2fsck/ |
| e2fsck.conf.5.in | 74 various filesystem inconsistencies.
86 interrupts e2fsck using ^C, and the filesystem is not explicitly flagged
93 e2fsck and/or formatting the filesystem initially. Normally this
106 filesystem checks (either based on time or number of mounts) should
126 This relation allows the message which is printed when this filesystem
131 whether this filesystem problem should be automatically fixed when
137 whether or not the filesystem will be marked as inconsistent if the user
146 whether or not the description for this filesystem problem should
153 whether or not the description for this filesystem problem should
171 number of directories in the filesystem are fewer than amount specified
[all...] |
| e2fsck.8.in | 45 to the filesystem before continuing with normal
47 processing. After the journal has been applied, a filesystem will
54 is the device file where the filesystem is stored (e.g.
70 are not valid if the filesystem is mounted. If
72 asks whether or not you should check a filesystem which is mounted,
91 filesystem's blocksize. For filesystems with 1k blocksizes, a backup
103 which specifies blocksize of the filesystem must be specified in order
107 the filesystem is not opened read-only, e2fsck will make sure that the
109 filesystem check.
138 so that the progress of the filesystem
[all...] |
