On: Fri, 10 Feb 2012 00:20:55 +0600 Roman Mamedov r...@romanrm.ru wrote
AFAIK the only reliable way currently to ensure the space after a
subvolume
deletion is freed, is to remount the FS.
Have You tried it Yourself? I think the problem was the remount
before the space has been completely
On Sat, 11 Feb 2012 14:47:15 +0100
Norbert Scheibner s...@gmx.net wrote:
Have You tried it Yourself? I think the problem was the remount
before the space has been completely freed in background. It
left a valid and working fs, with still work to do.
Yes, after some snapshot deletions the
The mount option -o recovery doesn't change anything, the segmentation
fault still occurs. Any ideas?
Daniel
cwillu wrote:
On Wed, Feb 8, 2012 at 4:19 PM, Daniel Kuhn che...@swissonline.ch wrote:
After a forced power turn-off the filesystem of my primary boot partition
cannot be mounted
On Sat, 11 Feb 2012 19:56:32 +0600 Roman Mamedov r...@romanrm.ru wrote:
Have You tried it Yourself? I think the problem was the remount
before the space has been completely freed in background. It
left a valid and working fs, with still work to do.
Yes, after some snapshot deletions the
On Fri, Feb 10, 2012 at 3:27 PM, Chris Mason chris.ma...@oracle.com wrote:
Ok, its worth pointing out that you're just one bit away from proper
ordering here. While I'm testing out this code to fix key ordering,
could you please run memtest86 on your machine?
I ran memtest for a good 16
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2012 12:48 AM, Duncan wrote:
So you see, a separate /boot really does have its uses. =:^)
True, but booting from removable media is easy too, and a full livecd gives
much more recovery options than the grub shell. It is the corrupted root
