From: Liu Bo <liubo2009@cn.fujitsu.com>
To: "Sergey E. Kolesnikov" <rockingdemon@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: trim malfunction in linux 3.3.6
Date: Fri, 18 May 2012 11:43:31 +0800 [thread overview]
Message-ID: <4FB5C563.9050203@cn.fujitsu.com> (raw)
In-Reply-To: <4FB522EC.50305@gmail.com>
On 05/18/2012 12:10 AM, Sergey E. Kolesnikov wrote:
> Hello.
> I've been running Ubuntu 12.04 kernel and btrfs on two partitions of two
> GPT partitioned SSDs. Rootfs was btrfs subvol "@" and homes were at
> "@home". When I was batch trimming with "fstrim /" using Ubuntu's
> standard kernel 3.2.0 - everything was fine. Then I compiled vanilla
> 3.3.6 kernel ad tried to fstrim again, fs got severely damaged.
>
> It seems that batch trim miscalculates ranges and trims some occupied
> space. Can't say if GPT or other partitioning details matter.
>
> I will try to provide any info possible, but fs is trimmed badly, and I
> need this machine to be up and running, so will have to mkfs.btrfs again
> and use 3.2.0 kernel.
>
> Steps that caused corruption:
> 1. Created partitions on two (say /dev/sd[ab]) SSD drives with about 1G
> offset from the beginning (first partition is ext4 for /boot)
> 2. mkfs.btrfs /dev/sd[ab]2
> 3. created subvolumes "@" and "@home" for mountpoints "/" and "/home"
> respectively
> 4. installed xubuntu 12.04
> 5. fstrim /
> 6. everything is ok
> 7. compiled and installed vanilla 3.3.6 kernel
> 8. reboot into 3.3.6
> 9. btrfs scrub - ok
> 10. fstrim /
> 11. fs got baaadly corrupted
Could you please show some logs about the corrpution?
I'll try to reproduce it on my own box. ;)
thanks,
liubo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-05-18 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 16:10 trim malfunction in linux 3.3.6 Sergey E. Kolesnikov
2012-05-17 18:31 ` Tomasz Torcz
2012-05-18 3:43 ` Liu Bo [this message]
2012-05-18 17:57 ` Sergey Kolesnikov
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=4FB5C563.9050203@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rockingdemon@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.