[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#707330: linux-image-3.8-1-amd64: Update to 3.8 causes MD RAID1 failure



On Thursday 09 May 2013, you wrote:
> On Thu, May 09, 2013 at 09:07:35AM +0200, Stefan Fritsch wrote:
> > I have two disks, one SSD and one HDD. There are to MD RAID1
> > volumes that each use one partition on the SSD and one on the
> > HDD.
> > 
> > After the first reboot with 3.8, MD kicked the HDD's partitions
> > from both RAID devices.
> 
> [...]
> 
> This sounds like a known bug that is fixed in 3.8.12.  md will
> send discard commands to both the SSD and the HDD, whereas it
> should of course send them to the SSD only.
> 
> Are you are using btrfs or ext4 filesystems with the 'discard'
> option? If so, does removing the option avoid this problem?

I am using ext4 but without either discard or nodiscard option. "grep 
discard /proc/mounts" gives no output (when running 3.2). According to 
the docs, nodiscard should be the default. So I guess it is not worth 
the effort to test with an explicit "nodiscard". Or has the default 
changed between 3.2 and 3.8? If so, Documentation/filesystems/ext4.txt 
is out of date.

More information which may or may not be helpful: md0 has ext4 on it 
without LVM (root partition). md1 is a LVM pv.


Reply to: