reiserfs and quota

Good evening!

I have an ispconfig (fully upgraded to the latest version) installation for the last couple of years and I am generally speaking happy with it. I am using it primarily for me and a couple of friends. It is installed in a debian server in a domU, per the instructions I followed in a relevant tutorial here in howtoforge. Both the dom0 and the domU run debian stable, both with the latest updates (dist-upgrade a couple of minutes ago).

My problem is that I could only boot the 2.6.35 kernel in the domU. Although the 3.2.0-4 kernel was installed in the domU properly, the computer froze during the booting process, right after the "reiserfs: using flush barriers" message (I still keep banging my head against the wall for choosing reiserfs for the server!). I googled for that problem but found no direct answer - just general statements about reiserfs instabilities, especially with quotas. I checked my fstab, which was as follows:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
devpts          /dev/pts        devpts  rw,noexec,nosuid,gid=5,mode=620 0  0
/dev/xvda1 none swap sw 0 0

/dev/xvda2 / reiserfs defaults,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0  0 1
/var/log/ispconfig/httpd/blahblah.net /var/www/clients/client3/web5/log    none    bind,nobootwait    0 0
/var/log/ispconfig/httpd/log.blah.org /var/www/clients/client2/web8/log    none    bind,nobootwait    0 0

To get the possibility of quota causing the problem out of the way, I changed the fstab as follows:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
devpts          /dev/pts        devpts  rw,noexec,nosuid,gid=5,mode=620 0  0
/dev/xvda1 none swap sw 0 0
/dev/xvda2 / reiserfs defaults  0 1

and now the domU can boot the 3.2.0-4 kernel with no problem at all!

I suspect that the lines I threw out of fstab were inserted by ispconfig. I checked the ispconfig panel and there are no quotas - limits neither for the websites nor for the mailboxes (I may have experimented with it in the past, but removed it right away - I cannot remember).

My questions are:
1. Is my fstab the way I have edited it OK or will it cause any problems to ispconfig and/or the functionality of the server?
2. Are there any configuration changes I must make in the ispconfig panel?
3. Will ispconfig try to re-edit the fstab?
4. Do you have any other suggestions / thoughts?

Thank you in advance for your help and thank you for such a nice piece of software and all the efforts you make to support it!

tsapi