From: Jeff Liu <jeff.liu@oracle.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: [PATCH v2 0/8] xfs: log space validation
Date: Fri, 17 May 2013 13:38:01 +0800 [thread overview]
Message-ID: <5195C239.5010905@oracle.com> (raw)
Hello,
This is version 2 of fix log space calculation if the log stripe unit is specified.
I changed the subject in this round since there are many changes belong to the log
space reservation interface adjustment.
Major changes of v2->v1:
- The interface of xfs_trans_reserve() has been changed to:
xfs_trans_reserve(struct xfs_trans *tp, xfs_trans_res *tres, int blocks, int rtextents);
- Introduce a new inline helper m_tresp() to fetch pointer of mp->m_reservations structure,
so that we don't need a big code change if someday we rename m_reservations to another
name.
- Introduce xfs_log_rlimit.[c|h] to isolate the maximum transaction log space validation
related routines. There are two functions can be shared with the user space which are:
void xfs_log_adjust_max_attrsetm_res();
void xfs_log_get_max_trans_res();
- Calculate the maximum length in bytes that would be required for a local attribute value
as large attributes out of line are not logged according to Dave's advise.
- Don't return if the given log space at mount time is too small, drop a message via syslog
in critical level instead.
Testing:
xfstests/generic and xfs specified test cases(except a dozens of cases need a tap device or
xfsdump) works without panic.
[PATCH 1/8] xfs: Introduce a new structure to hold transaction reservation items
[PATCH 2/8] xfs: Introduce tr_fsyncts to m_reservation
[PATCH 3/8] xfs: Make writeid transaction use tr_writeid
[PATCH 4/8] xfs: Refactor xfs_trans_reserve() interface
[PATCH 5/8] xfs: Get rid of all XFS_XXX_LOG_RES() macros
[PATCH 6/8] xfs: Refactor xfs_ticket_alloc() to extract a new helper
[PATCH 7/8] xfs: Add xfs_log_rlimit.[c|h]
[PATCH 8/8] xfs: Validate log space at mount time
The patches of user space sync up with those kernel space change will be sent out later as I
have to go out to deal with a urgent thing right now.
v1:
http://comments.gmane.org/gmane.comp.file-systems.xfs.general/52201
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-05-17 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 5:38 Jeff Liu [this message]
2013-06-14 1:59 ` [PATCH v2 0/8] xfs: log space validation Dave Chinner
2013-06-14 2:51 ` Jeff Liu
2013-06-14 3:08 ` Dave Chinner
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=5195C239.5010905@oracle.com \
--to=jeff.liu@oracle.com \
--cc=xfs@oss.sgi.com \
/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