Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Live Upgrade error file?

9 views
Skip to first unread message

pretzel

unread,
Jun 30, 2009, 2:01:50 PM6/30/09
to
I am doing a Live Upgrade on several nearly identical systems. It's
working great, but I am curious about a strange "lucopy.errors" file.
On one of my systems, the following "lucopy.error" file was generated:

0 blocks
0 blocks


That's it. The entire file. No files identified. Couldn't tell if
there was something that needed to be fixed. I ignored it and
everything went well (luupgrade, luactivate) and seems to be working
perfectly.

Can anyone tell me what those two mysterious lines in the
"lucopy.errors" file from lucreate?

Thank you.

DG

Alessandro Selli

unread,
Jun 30, 2009, 5:48:12 PM6/30/09
to
pretzel ha scritto:

http://www.linuxdynasty.org/opensolaris-live-upgrade-howto.html

Looks like this file contains a list of potential problems (issues)
that were encountered while populating the boot environment. 0 blocks
sounds reassuring to me.


Bye,


--
Alessandro Selli http://alessandro.route-add.net
AVVERTENZA: i messaggi inviati a "trappola" non mi arriveranno.
WARNING: messages sent to "trappola" will never reach me.
Chiave PGP/GPG key: EC885A8B

signature.asc

Alessandro Selli

unread,
Jun 30, 2009, 5:51:44 PM6/30/09
to
Alessandro Selli ha scritto:

> pretzel ha scritto:
>> I am doing a Live Upgrade on several nearly identical systems. It's
>> working great, but I am curious about a strange "lucopy.errors" file.
>> On one of my systems, the following "lucopy.error" file was generated:
>>
>> 0 blocks
>> 0 blocks
>>
>>
>> That's it. The entire file. No files identified. Couldn't tell if
>> there was something that needed to be fixed. I ignored it and
>> everything went well (luupgrade, luactivate) and seems to be working
>> perfectly.
>>
>> Can anyone tell me what those two mysterious lines in the
>> "lucopy.errors" file from lucreate?
>
> http://www.linuxdynasty.org/opensolaris-live-upgrade-howto.html
>
> Looks like this file contains a list of potential problems (issues)
> that were encountered while populating the boot environment. 0 blocks
> sounds reassuring to me.

In particular, these comments suggest lucreate just came scross,
maybe, two nonexistant files: «In general, you can ignore warnings about
files that were skipped because they did not exist or could not be
opened. You cannot ignore errors such as directories or files that could
not be created, or file systems running out of disk space.».

signature.asc

Tim Bradshaw

unread,
Jun 30, 2009, 6:41:39 PM6/30/09
to
On 2009-06-30 19:01:50 +0100, pretzel <david...@gmail.com> said:

> I am doing a Live Upgrade on several nearly identical systems. It's
> working great, but I am curious about a strange "lucopy.errors" file.
> On one of my systems, the following "lucopy.error" file was generated:
>
> 0 blocks
> 0 blocks

I'm not sure why this would happen, but one thing which I imagine might
cause it (and which can be a problem) is lucopy (which runs cpio I
think) coming across something it can't copy, and botching it. A good
example of that is a unix-domain socket, which will get turned into an
empty, ordinary, file. That can be bad.

Richard B. Gilbert

unread,
Jun 30, 2009, 7:06:33 PM6/30/09
to
Alessandro Selli wrote:
> pretzel ha scritto:
>> I am doing a Live Upgrade on several nearly identical systems. It's
>> working great, but I am curious about a strange "lucopy.errors" file.
>> On one of my systems, the following "lucopy.error" file was generated:
>>
>> 0 blocks
>> 0 blocks
>>
>>
>> That's it. The entire file. No files identified. Couldn't tell if
>> there was something that needed to be fixed. I ignored it and
>> everything went well (luupgrade, luactivate) and seems to be working
>> perfectly.
>>
>> Can anyone tell me what those two mysterious lines in the
>> "lucopy.errors" file from lucreate?
>
> http://www.linuxdynasty.org/opensolaris-live-upgrade-howto.html
>
> Looks like this file contains a list of potential problems (issues)
> that were encountered while populating the boot environment. 0 blocks
> sounds reassuring to me.
>
>
> Bye,
>
>

Somehow, I can't help thinking that this is an ass backwards way of
announcing success!

I'd much rather see something like "Live Upgrade successful: 0 Errors 1
Warning!

0 new messages