search for: lblock

...5-2.1: SerialNumber: 575532553130303530353538 Dec 26 21:41:04.191879 kernel: usb-storage 5-2.1:1.0: USB Mass Storage device detected Dec 26 21:41:13.365071 kernel: blk_partition_remap: fail for partition 1 Dec 26 21:41:13.365382 kernel: EXT4-fs warning (device sde1): dx_probe:744: inode #35151873: lblock 0: comm smbd: error -5 reading directory block Dec 26 21:41:13.365522 kernel: blk_partition_remap: fail for partition 1 Dec 26 21:41:13.365658 kernel: EXT4-fs warning (device sde1): dx_probe:744: inode #35151873: lblock 0: comm smbd: error -5 reading directory block Filesystem correctly reports th...

....g.: Buffer I/O error on device sdc1, logical block 3084285 After that it looks like the ext4 HD was unmounted automatically and the btrfs HD made this BUG: usb 2-1: USB disconnect, device number 2 EXT4-fs error (device sdc1): ext4_find_entry:935: inode #109051908: comm bash: reading directory lblock 0 EXT4-fs error (device sdc1): ext4_find_entry:935: inode #109051905: comm bash: reading directory lblock 0 EXT4-fs error (device sdc1): ext4_find_entry:935: inode #2: comm umount: reading directory lblock 0 lost page write due to I/O error on sdb1 lost page write due to I/O error on sdb1 lost...

...umber: 575532553130303530353538 > Dec 26 21:41:04.191879 kernel: usb-storage 5-2.1:1.0: USB Mass Storage device detected > Dec 26 21:41:13.365071 kernel: blk_partition_remap: fail for partition 1 > Dec 26 21:41:13.365382 kernel: EXT4-fs warning (device sde1): dx_probe:744: inode #35151873: lblock 0: comm smbd: error -5 reading directory block > Dec 26 21:41:13.365522 kernel: blk_partition_remap: fail for partition 1 > Dec 26 21:41:13.365658 kernel: EXT4-fs warning (device sde1): dx_probe:744: inode #35151873: lblock 0: comm smbd: error -5 reading directory block > > Filesystem...

...heck for UFS2 sb */ + if (do_checksb(sb, disk, UFS2_SBLOCK_OFFSET, UFS2_SUPER_MAGIC)) + return UFS2; + /* UFS2 may also exist in 256k-, but this isn't the default */ + if (do_checksb(sb, disk, UFS2_SBLOCK2_OFFSET, UFS2_SUPER_MAGIC)) + return UFS2_PIGGY; + + return NONE; +} + +/* + * lblock stands for linear block address, + * whereas pblock is the actual blk ptr to get data from. + * + * UFS1/2 use frag addrs rather than blk ones, then + * the offset into the block must be calculated. + */ +static const void * +ufs_get_cache(struct inode *inode, block_t lblock) +{ + const void *da...

...heck for UFS2 sb */ + if (do_checksb(sb, disk, UFS2_SBLOCK_OFFSET, UFS2_SUPER_MAGIC)) + return UFS2; + /* UFS2 may also exist in 256k-, but this isn't the default */ + if (do_checksb(sb, disk, UFS2_SBLOCK2_OFFSET, UFS2_SUPER_MAGIC)) + return UFS2_PIGGY; + + return NONE; +} + +/* + * lblock stands for linear block address, + * whereas pblock is the actual blk ptr to get data from. + * + * UFS1/2 use frag addrs rather than blk ones, then + * the offset into the block must be calculated. + */ +static const void * +ufs_get_cache(struct inode *inode, block_t lblock) +{ + const void *da...

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Wrote the documentation below. I think it would be good to push the doc to the wiki as soon as the UFS support gets merged. Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install) ----- There is a confusion about the name of this file system, then I decided to contact the author who replied: "The name has always been

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Change since v1: * Fix bug on dentry structure (thank you specification; btw, sarcasm), and consequently a bug on ufs_readdir. * Add readlink support (applied tests for symlinks whose destionation path were stored in blk pointers and the file itself). * Several improvements. Wrote the documentation below. I think it would be good to