Prev: Quick usb keyboard questions
Next: Backup software
From: Marc Heusser on 29 Jun 2007 14:29
In article <2007062117551043658-jollyroger(a)REMOVEpoboxcom>,
Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:

> On 2007-06-21 16:19:41 -0500, Marc Heusser
> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
>
> > In article <tacitr-E73BB5.22272018062007(a)netnews.comcast.net>,
> > tacit <tacitr(a)aol.com> wrote:
> >
> >> Try DiskWarrior. If that doesn't work, erase the volume and re-install
> >> your data from your backups.
> >
> > Thanks for the tip.
> >
> > I have DiskWarrior running - it has been running for 15 hours actually,
> > comparing directories now (about 300 GB of data, "7 million
> > comparisons"). Is it possible that it takes so long? Or do you suspect
> > an infinite loop?
>
> It takes that long - depending on how much data and fragmentation, it
> can take, literally, days. Don't touch it - let it do its thing.

It has been running now for a full week - 180 hours CPU, mostly
"comparing directories". In activity monitor it does appear normal
(not hung), and system CPU load on the 4 cores shifts from time to
time, which looks pretty normal. Still - is it possible that it runs
for so long, or is it in an infinite loop? When would you expect it
to finish?
Or what would you recommend to do? Restart the hard way? ...

TIA

Marc

--
Switzerland/Europe
<http://www.heusser.com>
remove CHEERS and from MERCIAL to get valid e-mail
From: Jolly Roger on 29 Jun 2007 16:28
On 2007-06-29 13:29:52 -0500, Marc Heusser
<marc.heusser(a)cheersheusser.commercialspammers.invalid> said:

> In article <2007062117551043658-jollyroger(a)REMOVEpoboxcom>,
> Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:
>
>> On 2007-06-21 16:19:41 -0500, Marc Heusser
>> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
>>
>>> In article <tacitr-E73BB5.22272018062007(a)netnews.comcast.net>,
>>> tacit <tacitr(a)aol.com> wrote:
>>>
>>>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
>>>> your data from your backups.
>>>
>>> Thanks for the tip.
>>>
>>> I have DiskWarrior running - it has been running for 15 hours actually,
>>> comparing directories now (about 300 GB of data, "7 million
>>> comparisons"). Is it possible that it takes so long? Or do you suspect
>>> an infinite loop?
>>
>> It takes that long - depending on how much data and fragmentation, it
>> can take, literally, days. Don't touch it - let it do its thing.
>
> It has been running now for a full week - 180 hours CPU, mostly
> "comparing directories". In activity monitor it does appear normal
> (not hung), and system CPU load on the 4 cores shifts from time to
> time, which looks pretty normal. Still - is it possible that it runs
> for so long, or is it in an infinite loop? When would you expect it
> to finish?
> Or what would you recommend to do? Restart the hard way? ...

Well, 300 GB is huge...

I don't own DiskWarrior. So I can't tell you how long 300 GB should
take. And I'm sure other factors can influence the speed (like
fragmentation, etc.).

If you are really concerned, give Alsoft a call and see what they think
about it.

--
JR

From: "Little Sir Echo" justwondering on 29 Jun 2007 16:37

On 29-Jun-2007, Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:

> On 2007-06-29 13:29:52 -0500, Marc Heusser
> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
>
> > In article <2007062117551043658-jollyroger(a)REMOVEpoboxcom>,
> > Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:
> >
> >> On 2007-06-21 16:19:41 -0500, Marc Heusser
> >> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
> >>
> >>> In article <tacitr-E73BB5.22272018062007(a)netnews.comcast.net>,
> >>> tacit <tacitr(a)aol.com> wrote:
> >>>
> >>>> Try DiskWarrior. If that doesn't work, erase the volume and
> >>>> re-install
> >>>> your data from your backups.
> >>>
> >>> Thanks for the tip.
> >>>
> >>> I have DiskWarrior running - it has been running for 15 hours
> >>> actually,
> >>> comparing directories now (about 300 GB of data, "7 million
> >>> comparisons"). Is it possible that it takes so long? Or do you suspect
> >>> an infinite loop?
> >>
> >> It takes that long - depending on how much data and fragmentation, it
> >> can take, literally, days. Don't touch it - let it do its thing.
> >
> > It has been running now for a full week - 180 hours CPU, mostly
> > "comparing directories". In activity monitor it does appear normal
> > (not hung), and system CPU load on the 4 cores shifts from time to
> > time, which looks pretty normal. Still - is it possible that it runs
> > for so long, or is it in an infinite loop? When would you expect it
> > to finish?
> > Or what would you recommend to do? Restart the hard way? ...
>
> Well, 300 GB is huge...
>
> I don't own DiskWarrior. So I can't tell you how long 300 GB should
> take. And I'm sure other factors can influence the speed (like
> fragmentation, etc.).
>
> If you are really concerned, give Alsoft a call and see what they think
> about it.
>
> --
> JR


I don't have a 300GB HD but I do have DiskWarrior.

Another factor to consider is the amount of free space on the disk.

The less that is available, the longer it takes DW to do its job.

Try JR's suggestion and call or email Alsoft; I have found them to be very
helpful.
From: Tom Stiller on 29 Jun 2007 17:49
In article <2007062915280743658-jollyroger(a)REMOVEpoboxcom>,
Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:

> On 2007-06-29 13:29:52 -0500, Marc Heusser
> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
>
> > In article <2007062117551043658-jollyroger(a)REMOVEpoboxcom>,
> > Jolly Roger <jollyroger(a)R.E.M.O.V.E.pobox.com> wrote:
> >
> >> On 2007-06-21 16:19:41 -0500, Marc Heusser
> >> <marc.heusser(a)cheersheusser.commercialspammers.invalid> said:
> >>
> >>> In article <tacitr-E73BB5.22272018062007(a)netnews.comcast.net>,
> >>> tacit <tacitr(a)aol.com> wrote:
> >>>
> >>>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
> >>>> your data from your backups.
> >>>
> >>> Thanks for the tip.
> >>>
> >>> I have DiskWarrior running - it has been running for 15 hours actually,
> >>> comparing directories now (about 300 GB of data, "7 million
> >>> comparisons"). Is it possible that it takes so long? Or do you suspect
> >>> an infinite loop?
> >>
> >> It takes that long - depending on how much data and fragmentation, it
> >> can take, literally, days. Don't touch it - let it do its thing.
> >
> > It has been running now for a full week - 180 hours CPU, mostly
> > "comparing directories". In activity monitor it does appear normal
> > (not hung), and system CPU load on the 4 cores shifts from time to
> > time, which looks pretty normal. Still - is it possible that it runs
> > for so long, or is it in an infinite loop? When would you expect it
> > to finish?
> > Or what would you recommend to do? Restart the hard way? ...
>
> Well, 300 GB is huge...
>
> I don't own DiskWarrior. So I can't tell you how long 300 GB should
> take. And I'm sure other factors can influence the speed (like
> fragmentation, etc.).

The only time I encountered comparable DiskWarrior run times was when
there were a large number of cross-linked files on the drive. It takes
a long time to run down the extent lists and safely allocate new extents
for the files. I shouldn't have to say it, but if cross-linked files
are recovered, their contents must be verified.
>
> If you are really concerned, give Alsoft a call and see what they think
> about it.
 | 
Pages: 1
Prev: Quick usb keyboard questions
Next: Backup software