On Mon, Apr 30, 2018 at 11:56 AM, Jayashree Mohan <jayashree2...@gmail.com> wrote: > Hi Jeff, > > On Mon, Apr 30, 2018 at 11:51 AM, Jeff Mahoney <je...@suse.com> wrote: >> On 4/30/18 12:04 PM, Vijay Chidambaram wrote: >>> Hi, >>> >>> We found two more cases where the btrfs behavior is a little strange. >>> In one case, an fsync-ed file goes missing after a crash. In the >>> other, a renamed file shows up in both directories after a crash. >> >> Hi Vijay - >> >> What kernel version did you observe these with? These seem like bugs >> Filipe has already fixed. >> >> -Jeff >> > > These bugs were observed on Kernel 4.16.0-041600-generic. >
To add on to what Jayashree said, these bugs are still present in the latest stable release of btrfs. We aren't sure if they have been patched on a development branch. We should note that similar bugs have been fixed before in btrfs, but those patches don't seem to handle these cases. -- 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
