search for: ext4_find_entri

I want to report a btrfs bug that happened this morning on kernel 3.2.1. I was copying a +5 GB file between two external usb harddisks, one formated with btrfs (the source) and the other with ext4 (the destination). In the meantime I decided to compile the 3.3-rc1 kernel with the output dir on the ext4 external harddisk. After some time I started to get many I/O errors coming from the ext4 drive

The most recent message is: [3108269.919256] sd 2:0:1:0: timing out command, waited 1080s [3108269.919528] sd 2:0:1:0: [sdb] Unhandled error code [3108269.919535] sd 2:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK [3108269.919540] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 00 01 21 47 00 00 08 00 [3108269.919586] EXT4-fs error (device sdb1): ext4_find_entry: reading directory #2 offset 0

Hi all, We've having an issue at the moment where an iSCSI connection was temporarily lost on a few VMs running CentOS 6 on ESXi. The problem is, now that the iSCSI connection has returned, we are not able to remount the drive. At first the drive is read-only, so I tried '*mount -o remount,rw*' which didn't work (still read-only), so then I tried a '*umount*' (which

Currently, some new storage devices have the ability to do performance optimizations according to the type of data payload - say, file system metadata, time-stamps, sequential write in some granularity, random write and so on. For example, the latest eMMC 4.5 device can support the so-called ''Context Management'' and ''Data Tag Mechanism'' features. By receiving