From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: List of filesystems to use generic checkpoint fops
Date: Fri, 27 Mar 2009 10:56:51 -0400 [thread overview]
Message-ID: <49CCE933.5050004@cs.columbia.edu> (raw)
In-Reply-To: <20090327040534.GB27803-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Matt Helsley wrote:
> In case anyone's curious here is my list of filesystems which I think should
> have generic_file_checkpoint fops (31):
Thanks, Matt.
> adfs
> affs
> befs
> bfs
> btrfs
> cramfs
> ecryptfs
> efs
> fat
> freevxfs
> hfs
> hfsplus
> hpfs
> hppfs
> isofs
> jffs2
> jfs
> minix
> ntfs
> omfs
> openpromfs
> qnx4
> ramfs
I'd think that in the case of ramfs we always need to dump the contents of the
file, or the entire file system, with the checkpoint image.
> reiserfs
> romfs
> squashfs
> sysv
> ubifs
> udf
> ufs
> xfs
>
> I also added the checkpoint operation to generic_ro_fops since it's used
> only in the set of filesystems listed above. For the curious:
> befs
> cramfs
> efs
> freevxfs
> isofs
> romfs
> squashfs
??
[...]
Oren.
next prev parent reply other threads:[~2009-03-27 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 4:05 List of filesystems to use generic checkpoint fops Matt Helsley
[not found] ` <20090327040534.GB27803-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-27 14:56 ` Oren Laadan [this message]
[not found] ` <49CCE933.5050004-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-03-27 15:19 ` Dave Hansen
2009-03-28 3:19 ` Matt Helsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CCE933.5050004@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox