On Mon, September 4, 2006 19:32, Les Mikesell wrote:
> On Mon, 2006-09-04 at 02:15, Sturla Holm Hansen wrote:
>
>> There are absolutely no difference in the output from "stat somesymlink"
>> before and after I have done "rm somesymlink; ln -s somepath ." where
>> the
>> somepath is the same as was
On Mon, 2006-09-04 at 13:25, David Koski wrote:
> I got several of these errors:
>
> Unable to read 2757426 bytes from /home/backuppc/pc/mail/new//f%2f/RStmp
> got=2287922, seekPosn=78452430 (4608,339,10001,80740352,81347343)
>
> I also see this in the kernel log:
>
> Sep 4 01:35:00 backup ker
I got several of these errors:
Unable to read 2757426 bytes from /home/backuppc/pc/mail/new//f%2f/RStmp
got=2287922, seekPosn=78452430 (4608,339,10001,80740352,81347343)
I also see this in the kernel log:
Sep 4 01:35:00 backup kernel: EXT3-fs error (device md(9,0)):
ext3_free_blocks: bit alre
On Mon, 2006-09-04 at 02:15, Sturla Holm Hansen wrote:
> There are absolutely no difference in the output from "stat somesymlink"
> before and after I have done "rm somesymlink; ln -s somepath ." where the
> somepath is the same as was reported from stat before I deleted the old
> symlink, it just
On Sat, September 2, 2006 05:20, Craig Barratt wrote:
> Sturla writes:
>
>> I restored to the same directory as the backup was taken from and the
>> symlinks LOOK ok when I stat them, but they just won't work.
>> If I delete the symlink and create it again with the info from stat it
>> works, but
