RE: Enabling quotas on an already existing file system



Yes, it is possible to use quotacheck on the filesystem which is mounted
in read-write mode. However, you should be sure that nobody is
performing write operations on the filesystem during the quotacheck run.
If there were write operations during the quotacheck run then the
filesystem usage data gathered by quotacheck may be incorrect for the
files affected by the write operations. For example, the sizes of the
changed files may be counted incorrectly, or some files created during
quotacheck may not be counted toward the user/group quotas at all, etc.

Alexey Fadyushin
Brainbench MVP for Linux.
http://www.brainbench.com

-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-
bounces@xxxxxxxxxx] On Behalf Of John O'Loughlin
Sent: Tuesday, June 27, 2006 6:37 PM
To: General Red Hat Linux discussion list
Subject: Re: Enabling quotas on an already existing file system


Actually ignore this, the -m option tells it not to remount read only.

John

On Tue, 27 Jun 2006, John O'Loughlin wrote:


Beware that quotacheck remounts the file system read only, so you
don't
want
to do this when you have any users logged on.

John

On Tue, 27 Jun 2006, Padiyath Sreekumaran wrote:


Hello,
OS : RedHat release 4

I have the following situation. At present I have a file system
Which is mounted without quota option and users are using it.
(/etc/fstab content:
/dev/vg00/ftp_data /data xfs defaults 1 2)

I want to implement userquota on this file system. I would like
to
know the following:

1. Can I implement quota on this file system?
2. If I can, Can I do the following:

a. unmount /data
b. mount with following command:
/dev/vg00/ftp_data /data xfs defaults,usrquota 1 2

c. quotacheck -avum

d. quotaon -a

d. then I will define the quota with "edquota username /data"



I donot know whether I have missed anything. I cannot make any
test on this production system.

Regards
Kumar


------------------------------------------------------------------
Padiyath Sreekumar | Tel: +41.56.310.3643
Paul Scherrer Institut | email: kumar.padiyath@xxxxxx
AIT | Office: WHGA/U132
WHGA/U132 | Fax: +41.56.310.3649
CH-5232 Villigen PSI |
Switzerland |
-----------------------------------------------------------------


--
redhat-list mailing list
unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


--
redhat-list mailing list
unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • RE: quota
    ... From my understanding, quotacheck reads ... however I'm unable to unmount the filesystem ... so instead I just use -f to force it to update the quota file... ... I guess noone uses quota that much or they just force it. ...
    (RedHat)
  • LVM, XFS and Quotas in Core 3
    ... I am unable to get LVM, XFS and quotas working in core 3. ... As far as I can tell, XFS is compiled with quota support, I have the ... proper fstab entries for each filesystem and I'm using stock ...
    (Fedora)
  • Disk Quota
    ... I am setting disk quota on '/' directory for each newly created group. ... and its giving me this error, quotacheck: ... or filesystem not mounted with quota option. ...
    (RedHat)
  • Re: Quotacheck failing
    ... FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: ... I have run a full fsck from single user mode on this volume and it ... comes up clean every time. ... recompile the quotacheck application to list the file entry ...
    (freebsd-questions)
  • [quota] quotacheck wont go with geom_label
    ... I found that a file system mounted through /dev/label/name doesn't ... It turned out that quotacheck after looking ... at fstab tries to open /dev/label/name and then receives EPERM, ...
    (freebsd-stable)