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

Bug#517828: marked as done (please document changed mount option for limiting disk usage with vservers)

Your message dated Sun, 23 Aug 2009 01:15:55 +0200
with message-id <20090822231555.GA25842@nekral.nekral.homelinux.net>
and subject line Re: Bug#517828: please document changed mount option for limiting disk usage with vservers
has caused the Debian Bug report #517828,
regarding please document changed mount option for limiting disk usage with vservers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
517828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517828
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: release-notes

Hi,

to use the disk limit feature of vserver (see 
http://linux-vserver.org/Disk_Limits_and_Quota) one had to use the mount 
option "tagxid" for a partition holding vserver guest filesystems with the 
2.6.18 kernel in etch.

With the 2.6.26 kernel in lenny this option has been renamed to "tag". If this 
isn't changed in /etc/fstab manually, the partition won't be mounted and thus 
the vservers wont start.

Please add this to the release notes for 5.0.1. 


Thanks,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message --- 
Hi,

On Mon, Mar 02, 2009 at 12:25:47PM +0100, Holger Levsen wrote:
> 
> to use the disk limit feature of vserver (see 
> http://linux-vserver.org/Disk_Limits_and_Quota) one had to use the mount 
> option "tagxid" for a partition holding vserver guest filesystems with the 
> 2.6.18 kernel in etch.
> 
> With the 2.6.26 kernel in lenny this option has been renamed to "tag". If this 
> isn't changed in /etc/fstab manually, the partition won't be mounted and thus 
> the vservers wont start.

Thanks for your report.

Based on your description, I committed the attached patch.

Best Regards,
-- 
Nekral

Index: en/issues.dbk
===================================================================
--- en/issues.dbk	(révision 6882)
+++ en/issues.dbk	(copie de travail)
@@ -612,4 +612,18 @@
     for more information.
   </para>
 </section>
+
+<section id="vserver_disk_limit">
+  <title>VServer Disk Limit</title>
+  <para>
+    To use the disk limit feature of vserver in &releasename;, you should
+    use the <command>mount</command> option <option>tag</option> (instead
+    of <option>tagxid</option> in &oldreleasename;).
+  </para>
+  <para>
+    You should manually update <filename>/etc/fstab</filename> and/or any
+    script which uses <option>tagxid</option>. Otherwise, the partition
+    will not be mounted and thus the vservers will not start.
+  </para>
+</section>
 </chapter>

--- End Message ---
Reply to: