From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-ext4@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: Re: journaled quota file question
Date: Sat, 31 Oct 2009 21:59:44 +0300 [thread overview]
Message-ID: <871vkj4cf3.fsf@openvz.org> (raw)
In-Reply-To: <871vkpwv4a.fsf@openvz.org>
Dmitry Monakhov <dmonakhov@openvz.org> writes:
> While looking to ext3/4 quota code I'm wondering
> Why do we have to place journaled quota file on fs root?
> In some situations it may be useful to place it deeper for example:
> /root/dir/quota_file
> The only reason what comes in to my mind is that some one
> may rename parent folder rename("/root/dir", "/root/dir2")
> Is this the only reason?
add an author in cc:
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-31 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 0:14 journaled quota file question Dmitry Monakhov
2009-10-31 18:59 ` Dmitry Monakhov [this message]
2009-11-02 12:31 ` Jan Kara
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=871vkj4cf3.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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