On Tue, 19 Dec 2006, Matthias Bertschy wrote:
> Otto Moerbeek wrote:
> > ulimit for memory usage is never unlimited. Look at ulimit -a. Check
> > the data size listed. To enlarge, change login.conf settings for
> > datasize-max and datasize-cur and don't forget to re-login.
> > The pax problem you are hitting could very well be memory-related too.
> > As a workaround, you might want to try to not copy the complete tree
> > in one go, but copy the various subirs separately. Or would that destroy
> > the hardlink structure?
> >
> > -Otto
> >
> I have modified my login.conf as shown:
> default:\
> :datasize-max=infinity:\
> :datasize-cur=750M:\
>
>
> And now pax -rw has been running for 24h, it is still not finished, but it
> hasn't crashed yet.
>
> So far 78.3GB have been written, but now the speed is ~1MB/s (maybe a lot of
> hardlinks are being written now).
> Top says:
> load averages: 2.11, 2.11, 2.08 10:45:03
> 37 processes: 36 idle, 1 on processor
> CPU states: 0.2% user, 0.0% nice, 0.5% system, 0.3% interrupt, 99.1% idle
> Memory: Real: 152M/242M act/tot Free: 762M Swap: 0K/2048M used/tot
>
> PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
> 9856 root -5 0 139M 139M sleep biowai 16:09 0.00% pax
>
> I will keep you informed. Thanks for the login.conf trick :-)
>
> Matthias
Ok, I assume you no longer have the core file you generated early. If
there's a bug i pax, I really like to fix it... I'll see if I can
reproduce the problem on a file system with lots of links and while
giving pax little memory.
-Otto
