[BlueOnyx:14020] Re: CMUImport issue

[Gustavo Silva]

On 03/11/2013 18:04, Michael Stauber wrote:
> Hi Gustavo,
>
>> Getting this strange issue while importing from old bluequartz to 5108
>> (both with 2.90 CMU)
>> Error displays on some users with large mboxes (4GB+)
>>
>> Creating user: c.santos
>> restoring archive for c.santos
>> ScanIn: Can't use string (201 OKsh: -c: line 1: unexpected EOF while
>> looking for matching `"'
>> sh: -c: line 2: syntax error: unexpected end of file
>> sh: -c: line 0: syntax error near unexpected token `)'
>> sh: -c: line 0: `echo -n "ScanIn: ") as a HASH ref while "strict refs"
>> in use at /usr/cmu/perl/Archive/Tar.pm line 624.'
> That error happens when there is a problem restoring the Tarball for
> that Vsite or user in question. There are a couple of reasons why this
> can happen:
>
> - The disk quota is incorrect. The user was created with a disk quota of
> (for example) 5GB, but the tarball contains 8GB of data. So there is
> insufficient space to restore it.
>
> - The tarball has been corrupted on transfer from the old server to the
> new one. Expecially multi-part tarballs (tarballs larger than 4GB are
> split into several parts) react very allergic to unpacking if one of
> them has been corrupted.
>
> The disk quota issue can be circumvented if you follow the CMU migration
> guide at this URL:
>
> http://www.blueonyx.it/index.php?page=cmu-migrations
>
> Especially follow the instructions outlined in step #2:
>
> 2.) Make sure no site or user is over quota (optional):
>
> Run this two commands as "root" from SSH:
>
> /usr/sausalito/sbin/disk_restorequotas.pl
> /usr/sbin/swatch
>
> The first command syncs the CODB stored quota settings for users and
> sites with the file system quota. The second command then checks the
> actual quota usage and stores it into CODB.
>
> Then go to the GUI, click on "Active Monitor" / "Status" / "Disk Usage"
> and check the "Sites" and "All users" tab to make sure that no site or
> user is over quota. If a site or user is over quota, increase their disk
> quota allowance until all sites and users are showing green.
>
>
Yes, this was the culprit.
Quates fixed, problem solved.
Many thanks!

Gustavo