after booting up my zone i get following error
Code:
# zlogin -C DB_zone
[Connected to zone 'DB_zone' console]
Sep 29 09:18:46 svc.startd[5680]: Could not log for
svc:/system/filesystem/root:default: write(51) failed with I/O error.
Sep 29 09:18:47 svc.startd[5680]: Could not log for
Sounds like there is a problem writing the to the log file for the services.
I would check you disks and make sure you have none failing. If you do a
svcs -l service_name you it will tell you where the log file is located.
On Tue, Sep 29, 2009 at 5:44 AM, Ketan techie...@gmail.com wrote:
after
Will Fiveash wrote:
As an aside it would be nice if the pkg image-update command provided
an option to update all zones configured in the BE being updated.
There is no option because it will eventually do that
automatically, just like upgrading s10 today will also
upgrade all zones. We're
Thanks to everyone that responded! Of the options presented, I
believe that the best option that will have the longest
supportability across Solaris and OpenSolaris versions over time is...
...create an rc script in the zone with the svcadm enable command
which removes itself after
Nicholas Senedzuk wrote:
Sounds like there is a problem writing the to the log file
for the services. I would check you disks and make sure you have none
failing. If you do a svcs -l service_name you it will tell you where
the log file is located.
Or where the service is
trying to write is
Edward Pilatowicz wrote:
- also, since the s10 brand is derived from the sn1 brand, could you
please ensure that all the new s10 brand that are being created are
derived from the corresponding sn1 brand files? ie, the s10 brand files
which are derived from sn1 brand files should be created via
