🚀 go-pugleaf

Two similar 670 systems running 4.1.3. Several new disks/partitions
added to each one... all is OK.

Reboot; suddenly several partitions (some of which existed before the
disk install) show up with wrong sizes, and/or as empty. 

umount -a. Then mount just one of those partitions. Is OK. umount it and
"mount -a". Same problem as before. umount -a followed by individual
mount of every filesystem - all OK. We can reproduce this, but don't
want to spend too much time doing so to narrow down the exact problem;
our users get a bit upset when we umount -a all the time.

Is there a known problem with "mount -a" related to the number of mount
points in fstab? (BTW, we don't use quotas or automounts if that
matters).

Please reply by email; I will post a summary.

 --------------------------------------------------------------------------
 | Adrian Booth					|	                  |
 | Adrian Booth Computing Consultants		|   Ph/Fax: (09) 354 4936 |
 | 7 Glenrowan Pl., Willetton WA 6155		|	abcc@DIALix.oz.au |
 | AUSTRALIA                                    |                         |
 --------------------------------------------------------------------------
for a in past present future; do
	for b in clients employers associates relatives neighbours pets; do
echo The opinions in this article in no way reflect the opinions of my $a $b.
done;done