[DFG T3.0] Internal error - VMS

This is a discussion on [DFG T3.0] Internal error - VMS ; Does anyone know if the field test for DFG 3 has ended already? I still use T3.0 (on OpenVMS Alpha V8.3 with all current ECOs) and I just got an abort of a /LEVEL=1 defragmentation (right after the start): %DFG-W-INTERR, ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: [DFG T3.0] Internal error

  1. [DFG T3.0] Internal error

    Does anyone know if the field test for DFG 3 has ended already?
    I still use T3.0 (on OpenVMS Alpha V8.3 with all current ECOs) and I just
    got an abort of a /LEVEL=1 defragmentation (right after the start):

    %DFG-W-INTERR, internal error: directory_name_match: pattern starts wrong
    %DFG-F-INTERR, internal error

    and

    %DFG-W-UNCRECOVERR, unrecoverable error
    Target volume was DISK$mumble (_DSA0

    Any comments?

    -EPLAN

    PS: I just noted that I've error log entries, means it could be a h/w issue...
    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  2. Re: [DFG T3.0] Internal error

    what is the diff of dfg versus dfu ? I am using dfu 3.2 on openVMS alpha
    8.3

    "Peter 'EPLAN' LANGSTOeGER" wrote in message
    news:474ef284$1@news.langstoeger.at...
    > Does anyone know if the field test for DFG 3 has ended already?
    > I still use T3.0 (on OpenVMS Alpha V8.3 with all current ECOs) and I just
    > got an abort of a /LEVEL=1 defragmentation (right after the start):
    >
    > %DFG-W-INTERR, internal error: directory_name_match: pattern starts wrong
    > %DFG-F-INTERR, internal error
    >
    > and
    >
    > %DFG-W-UNCRECOVERR, unrecoverable error
    > Target volume was DISK$mumble (_DSA0
    >
    > Any comments?
    >
    > -EPLAN
    >
    > PS: I just noted that I've error log entries, means it could be a h/w
    > issue...
    > --
    > Peter "EPLAN" LANGSTOEGER
    > Network and OpenVMS system specialist
    > E-mail peter@langstoeger.at
    > A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist




  3. Re: [DFG T3.0] Internal error

    In article <474ef284$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) writes:
    >
    >
    >Does anyone know if the field test for DFG 3 has ended already?
    >I still use T3.0 (on OpenVMS Alpha V8.3 with all current ECOs) and I just
    >got an abort of a /LEVEL=1 defragmentation (right after the start):
    >
    >%DFG-W-INTERR, internal error: directory_name_match: pattern starts wrong
    >%DFG-F-INTERR, internal error
    >
    >and
    >
    >%DFG-W-UNCRECOVERR, unrecoverable error
    >Target volume was DISK$mumble (_DSA0
    >
    >Any comments?


    Not about the DFG field test per se but doesn't it always seem that you
    uncover a bug after the end of the formal field test? I found a couple
    of them during some VMS V7.* field tests after the end of the field test.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  4. Re: [DFG T3.0] Internal error

    In article , VAXman- @SendSpamHere.ORG writes:
    >In article <474ef284$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) writes:
    >>
    >>Does anyone know if the field test for DFG 3 has ended already?
    >>I still use T3.0 (on OpenVMS Alpha V8.3 with all current ECOs) and I just
    >>got an abort of a /LEVEL=1 defragmentation (right after the start):
    >>
    >>%DFG-W-INTERR, internal error: directory_name_match: pattern starts wrong
    >>%DFG-F-INTERR, internal error
    >>
    >>and
    >>
    >>%DFG-W-UNCRECOVERR, unrecoverable error
    >>Target volume was DISK$mumble (_DSA0
    >>
    >>Any comments?

    >
    >Not about the DFG field test per se but doesn't it always seem that you
    >uncover a bug after the end of the formal field test? I found a couple
    >of them during some VMS V7.* field tests after the end of the field test.


    Not always.
    (I found a lot of bugs in TCPware V5.8 BIND9 and FT is still running ;-)

    Could be that GNV V2.1 was the culprit. I removed it, to remove the annoying
    endless loop ([VMS$COMMON.GNV.MNT.sysdevdiskvolnam.000000.000000. 000000...])
    to get a simple sysdisk PURGE working again, and now DFG works as I know it.
    Maybe, I find the time to prove this first assumption...

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  5. GNV V2.1 (was: Re: [DFG T3.0] Internal error)

    Peter 'EPLAN' LANGSTOeGER wrote:
    [...]
    > Could be that GNV V2.1 was the culprit. I removed it, to remove the annoying
    > endless loop ([VMS$COMMON.GNV.MNT.sysdevdiskvolnam.000000.000000. 000000...])
    > to get a simple sysdisk PURGE working again, and now DFG works as I know it.
    > Maybe, I find the time to prove this first assumption...


    They still haven't fixed GNV? I ran into the same problem in V2.0 and
    earlier. I thought I was pretty smart not to install it on the system
    disk when I was first using it, but I trashed my home directory (and
    everything else on the GNV disk) by trying to remove GNV when I ran
    across the "endless loop" problem - luckily, I had a pre-GNV backup.

    I downloaded V2.1 recently to see if the problem might have been
    resolved by now. Thanks for the heads-up!

  6. Re: GNV V2.1 (was: Re: [DFG T3.0] Internal error)

    DFG V3.0 has been released on the Septemer 2007 CD kit.

    regards Kalle

  7. Re: GNV V2.1 (was: Re: [DFG T3.0] Internal error)

    In article <474F5C60.7090707@comcast.net>, bradhamilton writes:
    >Peter 'EPLAN' LANGSTOeGER wrote:
    >[...]
    >> Could be that GNV V2.1 was the culprit. I removed it, to remove the annoying
    >> endless loop ([VMS$COMMON.GNV.MNT.sysdevdiskvolnam.000000.000000. 000000...])
    >> to get a simple sysdisk PURGE working again, and now DFG works as I know it.
    >> Maybe, I find the time to prove this first assumption...

    >
    >They still haven't fixed GNV? I ran into the same problem in V2.0 and
    >earlier. I thought I was pretty smart not to install it on the system
    >disk when I was first using it, but I trashed my home directory (and
    >everything else on the GNV disk) by trying to remove GNV when I ran
    >across the "endless loop" problem - luckily, I had a pre-GNV backup.


    I successfully removed GNV V2.1, so at least, the deinstall problem is
    fixed (I trashed one system disk during GNV V2.0, too) but the endless
    loop problem is still there and I don't know how the solution will be then.
    I still don't see the real need for $ SET ROOT, but I see now a need for
    some modifiers or a modifier lexical function for the F$SEARCH one
    (or the other wildcard RMS functions which eg. the DIRECTORY command uses)...

    >I downloaded V2.1 recently to see if the problem might have been
    >resolved by now. Thanks for the heads-up!


    One needs to manually remove the [GNV.MNT]*.DIR links (don't know how, yet)
    and then GNV might still work, but the other problems should be gone. Right?

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  8. Re: [DFG T3.0] Internal error

    In article , "Jerry Alan Braga" writes:
    >what is the diff of dfg versus dfu ? I am using dfu 3.2 on openVMS alpha
    >8.3


    DFG is DEFRAGger or (supported) Disk File Optimizer (DFO) of VMS engineering.
    DFU are the Disk&File Utilities (Freeware) of a former VMS engineer
    (which - like LDDRIVER - is now homed at http://www.digiater.nl)

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

+ Reply to Thread