Re: [PATCH] e2image: Print a warning if running over a mounted filesystem

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

 



On Thu, Sep 26, 2013 at 06:00:04PM -0300, Carlos Maiolino wrote:
> Several users use to run e2image over a mounted filesystem, providing
> inconsistent, useless e2images.
> This patch adds a warning in such cases, notifying the user and also adds a
> force option making e2image able to run over Read-only filesystems.

It should be perfectly safe to run e2image on a read-only mounted file
system option, so it's not obvious to me why the force option would be
needed in that case.

Also, if we are saving a "normal" (not a raw or qcow) e2image file, we
are only backing up the statically located metadata blocks (i.e.,
superblock, block group descriptors, inode table, and allocation
bitmaps).  If we do this on a mounted file system, the e2image file is
less useful, but I'm not sure I'd call it completely useless.  If the
goal is to backup critical metadata, it will do that just fine.  So
maybe it's worthy of a warning, but I'm not sure it should require a
force option.

If the user is trying to capture a raw or qcow image file, I agree
that requiring that the file systme either be mounted read-only, not
mounted at all, or that a force option be specified, makes sense.

	   	   	  	       	  - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux