On Sat, Sep 1, 2012 at 11:23 AM, Shentino <shentino@xxxxxxxxx> wrote: > On Sat, Sep 1, 2012 at 8:41 AM, Michael <mike@xxxxxxxxxx> wrote: >> Please make sure you are running a very recent kernel. Btrfs is VERY >> active and fixes for things like this are going in all the time. Any >> related crash errors, kernel oopses, and exact methodology so we can >> reproduce would be useful. >> dmesg and uname -a would help us triage this and see what we need to fix. >> Mike > > I did save debug information like this, on a separate filesystem no > less...unfortunately I was unable to sync and it disappeared when I > was forced to cold boot. I don't have a spare machine available. > > To reproduce: > > 1. lvcreate vg --name lv --size 1G > 2. mkbtrfs -M /dev/vg/lv > 3. mkdir /mnt/test > 4. mount /dev/vg/lv /mnt/test > 5. dd bs=1024 count=1 < /dev/urandom > /tmp/foo > 6. sha1sum /tmp/foo > /mnt/test/scrubme > 7. sync (get /mnt/test/scrubme written to disk) > 8. sed -e "s/the_sha1_sum/something_else_of_same_length/" < > /dev/vg/lv > /dev/vg/lv > 9. cat /mnt/test/scrubme (returns I/O error as expected, probably > from a failed checksum) > 9. btrfs scrub /mnt/test > > This is when all hell breaks loose. > > Will this be enough information to at least allow it to be reproduced > or check if the bug still exists? You still haven't said which kernel you were running; the thing to do is try the very latest rc (if not btrfs-next). -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
