On Thu, 7 Aug 2008, Adrian Chadd wrote:
It -should- just run the create command over each storedir and create
missing ones; it might even create missing directories in each
storedir.
We've done it many times both in 2.6 and 2.7 with mixed stores of aufs +
coss and it HAS behaved as described above (i.e. only creates missing
ones and not touch existing + add extra subdirectories if missing)
I do like the idea of using the dummy squid.conf for the -z operation to
minimize service outage...
adrian
2008/8/6 Amos Jeffries <squid3@xxxxxxxxxxxxx>:
Adrian Chadd wrote:
The upgrade should go smoothly. A 2.6 ufs/aufs/diskd store should work
fine in 2.7.
Also our upgrade from 2.6 to 2.7 went smoothly. :)
Adrian do you know what the behavior on -z is for a mix of existing and
absent cache_dirs?
Amos
Adrian
2008/8/6 Amos Jeffries <squid3@xxxxxxxxxxxxx>:
Mr. Issa(*) wrote:
Hello all , i really appretiate your hard work on helping and guiding
users all over the word..:)
I have 2 questions:
If i want to add another hard-disk and to set it as a cache_dir for
squid to use, but without messing/rebuildings the other cache_dir's
that have cached objects
second question , i want to upgrade squid from 2.6 to 2.7 and let
squid 2.7 to use the cache_dir's that have cached objects without
rebuilding them
-z should ignore the existing cache_dir and build the new one.
However I'm not certain enough of the store to guarantee that.
To be extra safe you could do the following:
- create a dummy squid.conf with just the new cache_dir.
- run squid binary with -z and passing it the dummy squid.conf
(to create new dir properly in isolation)
- add the new cache_dir to real squid.conf and reconfigure main squid.
As for the upgrade. A lot of work has gone into making those go smoothly.
I
believe its not a problem. But maybe one of the Squid-2 store experts
will
speak up.
Amos
--
Please use Squid 2.7.STABLE3 or 3.0.STABLE8
--
Please use Squid 2.7.STABLE3 or 3.0.STABLE8
--
