On 09.07.2011 18:19, cac...@quantum-sci.com wrote: > Just compiled a custom kernel, but unable to mount a btrfs partition. It > essentially says 'unrecognized filesystem'. What could be missing? > > # File systems > # > CONFIG_EXT2_FS=y > CONFIG_EXT2_FS_XATTR=y > CONFIG_EXT2_FS_POSIX_ACL=y > CONFIG_EXT2_FS_SECURITY=y > # CONFIG_EXT2_FS_XIP is not set > CONFIG_EXT3_FS=y > CONFIG_EXT3_DEFAULTS_TO_ORDERED=y > CONFIG_EXT3_FS_XATTR=y > CONFIG_EXT3_FS_POSIX_ACL=y > CONFIG_EXT3_FS_SECURITY=y > CONFIG_EXT4_FS=y > CONFIG_EXT4_FS_XATTR=y > # CONFIG_EXT4_FS_POSIX_ACL is not set > # CONFIG_EXT4_FS_SECURITY is not set > # CONFIG_EXT4_DEBUG is not set > CONFIG_JBD=y > # CONFIG_JBD_DEBUG is not set > CONFIG_JBD2=y > # CONFIG_JBD2_DEBUG is not set > CONFIG_FS_MBCACHE=y > # CONFIG_REISERFS_FS is not set > CONFIG_JFS_FS=y > # CONFIG_JFS_POSIX_ACL is not set > # CONFIG_JFS_SECURITY is not set > # CONFIG_JFS_DEBUG is not set > # CONFIG_JFS_STATISTICS is not set > # CONFIG_XFS_FS is not set > # CONFIG_GFS2_FS is not set > # CONFIG_OCFS2_FS is not set > CONFIG_BTRFS_FS=y > CONFIG_BTRFS_FS_POSIX_ACL=y > # CONFIG_NILFS2_FS is not set > CONFIG_FS_POSIX_ACL=y > CONFIG_FILE_LOCKING=y > CONFIG_FSNOTIFY=y > CONFIG_DNOTIFY=y > CONFIG_INOTIFY_USER=y > # CONFIG_FANOTIFY is not set > CONFIG_QUOTA=y > CONFIG_QUOTA_NETLINK_INTERFACE=y > CONFIG_PRINT_QUOTA_WARNING=y > # CONFIG_QUOTA_DEBUG is not set > CONFIG_QUOTA_TREE=m > # CONFIG_QFMT_V1 is not set > CONFIG_QFMT_V2=m > CONFIG_QUOTACTL=y > CONFIG_QUOTACTL_COMPAT=y > CONFIG_AUTOFS4_FS=y > CONFIG_FUSE_FS=y > CONFIG_CUSE=y > CONFIG_GENERIC_ACL=y If your btrfs lives on two or more devices you will have to run 'btrfs device scan' prior to mount or give all devices as arguments to mount.btrfs.
Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
