So, I examined the below filesystem, the one of the two that I would
really like to restore. There is basically nothing but zeros, and
very occasionally a sparse string of data, until exactly 0x20
offset, at which point the data is suddenly very packed and looks like
usual compressed data
Hi,
tl;dr: btrfs_trim_fs, IMHO, needs more thorough surgery.
Thanks for providing the new patch. I think it will work in the case
that fstrim is called without specifying a range to trim (that is,
defaulting to the whole filesystem), but I didn't test that yet, sorry.
Instead, I have been
Phillip Susi posted on Sat, 11 Feb 2012 19:04:41 -0500 as excerpted:
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.
On Thu, Feb 02, 2012 at 07:27:22AM -0800, Marc MERLIN wrote:
On Thu, Feb 02, 2012 at 07:42:41AM -0500, Chris Mason wrote:
On Wed, Feb 01, 2012 at 07:23:45PM -0800, Marc MERLIN wrote:
On Wed, Feb 01, 2012 at 12:56:24PM -0500, Chris Mason wrote:
Second, I was wondering if anyone is
On 02/12/2012 11:32 PM, Marc MERLIN wrote:
Actually I had one more question.
I read this page:
http://www.redhat.com/archives/dm-devel/2011-July/msg00042.html
I'm not super clear if with 3.2.5 kernel, I need to pass the special
allow_discards option for brtfs and dm-crypt to be safe together,
On Fri, Feb 10, 2012 at 3:33 AM, Jan Schmidt list.bt...@jan-o-sch.net wrote:
Hi Mitch,
having this patch on the list is a good idea. I've two remarks, just in
case it will be included sometimes:
On 09.02.2012 22:38, Mitch Harder wrote:
diff --git a/fs/btrfs/delayed-inode.c
On Mon, Feb 13, 2012 at 12:47:54AM +0100, Milan Broz wrote:
On 02/12/2012 11:32 PM, Marc MERLIN wrote:
Actually I had one more question.
I read this page:
http://www.redhat.com/archives/dm-devel/2011-July/msg00042.html
I'm not super clear if with 3.2.5 kernel, I need to pass the special
On 02/13/2012 01:01 AM, Lutz Euler wrote:
Hi,
tl;dr: btrfs_trim_fs, IMHO, needs more thorough surgery.
Thanks for providing the new patch. I think it will work in the case
that fstrim is called without specifying a range to trim (that is,
defaulting to the whole filesystem), but I didn't
Hello,
is it possible to set nodatacow on a per-file basis? I couldn't find
anything.
If not, wouldn't that be a great feature to get around the performance
issues with VM and database storage? Of course cloning should still
cause COW.
Thanks,
Ralf-Peter
--
To unsubscribe from this list:
