Hi Dave,
We will submit patches for the rest of the tests soon. We are working on it.
Thanks,
Jayashree Mohan
Thanks,
Jayashree Mohan
On Thu, Mar 7, 2019 at 2:22 PM Dave Chinner wrote:
>
> On Thu, Mar 07, 2019 at 09:12:06AM +0200, Amir Goldstein wrote:
> > On Thu, Mar 7, 2019
Hi Jaegeuk,
Thanks for the quick reply!
On Tue, Apr 24, 2018 at 11:48 PM Jaegeuk Kim wrote:
>
> Hi,
>
> On 04/24, Jayashree Mohan wrote:
> > Hi,
> >
> > While testing filesystems for crash consistency, we came across a
> > workload that could demonstr
adata behaviour, shouldn't it correctly persist the rename in this
case? Let us know what you think about this inconsistent behaviour.
Thanks,
Jayashree Mohan
--
Check out the vibrant tech community on one of the wo
Hey Dave,
Thanks for clarifying the crash recovery semantics of strictly
metadata ordered filesystems. We had a follow-up question in this
case.
On Fri, Apr 13, 2018 at 8:16 AM, Amir Goldstein wrote:
> On Fri, Apr 13, 2018 at 3:54 PM, Vijay Chidambaram
> wrote:
>> Hi Amir,
>>
>> Thanks for the
.
Thanks,
Jayashree Mohan
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Linux-f2fs-devel ma
acknowledge if the above reported
test scenario is considered a bug or not. If not, could you explain
why it's okay to do so?
[1] https://github.com/utsaslab/crashmonkey
Thanks,
Jayashree
On Wed, Feb 21, 2018 at 12:18 PM, Jayashree Mohan
wrote:
> Hi,
>
> I am Jayashree Mohan, a
Hi,
I am Jayashree Mohan, a PhD student at the University of Texas at
Austin, working with Prof. Vijay Chidambaram. I've been working on the
Crashmonkey project, which is a test harness for file system crash
consistency checks[1].
Using CrashMonkey, we stumbled upon the following possible
