>> cache. It's supposed to fail. Bcache will(?) properly handle a busted SSD.
> > The doumentation says no and recommends a RAID. That's the reason > why it is used in WriteThrough mode per default. 'busted' in this case means errors on write. If the device disappears and is no longer readable, then sure any un-committed blocks are gone and your filesystem/file is broken. On write failure (how many?) I would sure hope the code-path marks the malfunctioning SSD as disabled and just sends the writes to the HDD. Whether it then gets more aggressive about de-staging previously staged writes I don't know (probably not) but just as long as the SSD is readable the dirty blocks can be written out. If you're not running kernel 3.11.5 (or 3.11.4 with *all* the bcache fixes) you're wasting your time. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
