From: Trevor Higgins <plan9fullfrontal@qs.co.nz>
To: 9front@9front.org
Subject: Re: [9front] Help wanted tracking down a bug in divergefs code [Demonstration code]
Date: Thu, 20 Feb 2020 14:08:17 +1300 [thread overview]
Message-ID: <29e75b4f-8490-a93e-1df1-adc4443e71d8@qs.co.nz> (raw)
In-Reply-To: <B93CDDDD6F897B854E81C358527CF119@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On 02/17/2020 06:59 PM, ori@eigenstate.org wrote:
>> Any way, any ideas on where I can put more fprints to track down which
>> bit of code is in the wrong?
> The first step: find as small a repro for this bug as you can. And then
> post it (ideally as a script) so that someeone else can test it.
>
I have attached small tar file of test, as I was testing using a config
file, i have stripped down the test config to bare minimum
--
We need another plan
[-- Attachment #2: demo-bug-mkfs+divergefs.tgz --]
[-- Type: application/x-compressed-tar, Size: 872 bytes --]
next prev parent reply other threads:[~2020-02-20 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 9:18 Help wanted tracking down a bug in divergefs code Trevor Higgins
2020-02-17 5:59 ` [9front] " ori
2020-02-20 1:08 ` Trevor Higgins [this message]
2020-02-17 15:44 ` kvik
2020-02-17 20:03 ` raingloom
2020-02-19 23:50 ` raingloom
2020-02-20 1:25 ` [9front] Help wanted tracking down a bug in divergefs code [unionfs] Trevor Higgins
2020-02-20 11:21 ` kvik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29e75b4f-8490-a93e-1df1-adc4443e71d8@qs.co.nz \
--to=plan9fullfrontal@qs.co.nz \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).