DragonFly BSD
DragonFly bugs List (threaded) for 2011-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[issue1990] /mnt too large to mount

From: "Thomas Nikolajsen \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 16 Feb 2011 23:24:55 +0000

Thomas Nikolajsen <thomas.nikolajsen@mail.dk> added the comment:

>Re: [issue1984] hammer mount fails after crash - HAMMER: FIFO record badhead 
signature ..
>From: "Diegu" <peur.neu@xxxxxxxxx> 
>Date: Tue, 15 Feb 2011 17:35:39 +0100 
>looks quite similar to my stuff.
Yes both issues seems to be jammed UNDO/REDO FIFO;
what is your system like:
HAMMER file system size, RAM amount, DragonFly version, i386 or x86_64?

>have you tried to flush the PFS from another fresh install ?
What do you mean by 'flush the PFS'?
I tried to mount HAMMER file system from another DragonFly install
(as affected FS was root FS); result is described in issue1984.

>theres no flushing without a master/slave PFS then you need a fresh install
>to prove the point right?
I'm still not sure what you mean by 'flushing'.

>i´ve tried to prune over a RO but it seems not possible.
>by the way. HAMMER recovery works for me but it won´t save the prev install.
Well, if FS is mounted RO it makes a lot of sense that it can't be modified,
like pruned.
If data can be read from RO mount, you can recover by just copy data to
another disk (or other partition on same disk); this won't save history.
Using 'hammer recover' could be used to the same effect.

Lets see which diagnose Matt does; FS will hopefully be revived.


DragonFly issue tracker <bugs@lists.dragonflybsd.org>

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