Lines Matching full:filesystem
164 * Check to see if a filesystem is in /proc/filesystems.
201 * Check to see if a filesystem is available as a module
333 * If the filesystem does not have a journal and ext2 and ext4
335 * ext4dev filesystem.
345 * If the filesystem is marked as OK for use by in-development
346 * filesystem code, but ext4dev is not supported, and ext4 is,
350 * If the filesystem is marked as in use by production
351 * filesystem, then it can only be used by ext4 and NOT by
377 * If the filesystem does not have a journal and ext2 is not
379 * filesystem.
396 * If the filesystem is a OK for use by in-development
397 * filesystem code, and ext4dev is supported or ext4 is not
399 * the detection and mark the filesystem as ext4dev.
401 * If the filesystem is marked as in use by production
402 * filesystem, then it can only be used by ext4 and NOT by
634 * The FAT filesystem could be without a magic string in superblock
669 * FAT12/16 filesystem magic field identifier, and if they are
670 * present, we rule this out as a FAT filesystem, despite the
1402 * Various filesystem magics that we can check for. Note that kboff and
1613 * Zap the device filesystem information and try again
