Re: dm-cache refusing to come up again after a crash

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

 



On Fri, Dec 06, 2013 at 08:53:10PM +0100, Steinar H. Gunderson wrote:
> <superblock uuid="" block_size="512" nr_cache_blocks="865560" policy="cleaner" hint_width="4">
>   <mappings>
>     <mapping cache_block="0" origin_block="6118373" dirty="false"/>
>     <mapping cache_block="1" origin_block="6118275" dirty="false"/>
>     <mapping cache_block="2" origin_block="5934780" dirty="false"/>
> [... lots of blocks, none of them dirty ...]
>     <mapping cache_block="505877" origin_block="889613" dirty="false"/>
>     <mapping cache_block="505878" origin_block="690575" dirty="false"/>
>     <mapping cache_block="505879" origin_block="875752" dirty="false"/>
>   </mappings>

OK, so since all blocks were marked as non-dirty, I wiped the metadata
volume, which made the system boot just fine, but was seemingly a big
mistake; a lot of filesystems had more or less fatal errors.

I'm restoring from backup right now. (Yes, I have them.)

/* Steinar */
-- 
Homepage: http://www.sesse.net/

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux