Solaris 10. df -h / ?

Должно хватить простого ребута.

>за зря на http://www.timrom.co.il не ходите он не русский :-)

Чуть не сломал глаза

ребут делали дважды, не помогло.

А так просто fsck запустить не пробовали?

>Я пока вижу только вариант загрузки с CD и запуска fsck

Ну так наверное лучше всего, а то может fsck поврежденный. Хотя вроде в single user mode можно попробовать.

>Какова причина?

Сейчас на все глюки ФС одна причнина --- Проклятие Крона :)

Если есть косяки на ФС - будут следы в /var/adm/messages. Если нет, то скорее всего надо установить last recommended patch cluster. Дело скорее всего в патчах. По-моему что-то подобное как-то в алертах пролетало

Гугл ниасилил перевод , ну и стандартно - шрифтыыы !



По сажбу какая там FS ?

ufs

Пожалуй да, лучший вариант это загрузка с CD с последующими проверками.

По-моему ваш вариант:
Document Audience: PUBLIC
Document ID: 201271
Old Document ID: (formerly 102899)
Title: Kernel Patches Cause "df -k" Output to Show Unrealistic Values With UFS Logging Enabled
Copyright Notice: Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Fri May 25 00:00:00 MDT 2007
Solution Type Sun Alert
Solution 201271 : Kernel Patches Cause "df -k" Output to Show Unrealistic Values With UFS Logging Enabled
Related Categories
Home>Content>Sun Alert Criteria Categories>Availability

Home>Content>Sun Alert Release Phase>Resolved



Previously Published As
102899
Product
Solaris 10 Operating System
Bug ID
6453594
Date of Workaround Release
27-APR-2007
Date of Resolved Release
25-MAY-2007
SA Document Body
QFHHJKG Internal ID use only.
Impact
When kernel patches 118822-23 (or later) for SPARC and 118844-23 (or later) for x86 are installed on a system with UFS logging enabled, the output of "df -k" shows unrealistic values.
Contributing Factors
This issue can occur in the following releases:
SPARC Platform
Solaris 10 with patch 118822-23 or later and without patch 124258-05
x86 Platform
Solaris 10 with patch 118844-23 or later and without patch 124259-05
Note 1: Solaris 8 and Solaris 9 are not impacted by this issue.
Note 2: This issue only impacts systems on which UFS logging is enabled.
To determine if logging is enabled on a file system(s), the following command can be run (this will return one line per file system that has "logging" in its entry):
$ mount | grep logging
/local on /dev/dsk/c0t0d0s1
read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=22000 09 on Wed Sep 14 18:50:41 2005
/local on /dev/dsk/c0t0d0s1
read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=22000 09 on Wed Sep 14 18:50:41 2005

In the above example, both "/" and "/local" file systems have logging enabled. If the logging option is not present, the system is not vulnerable to this issue.

Symptoms
Should the described issue occur, output of "df -k" will be unrealistic. That is, fields of "df" such as "kbytes", "used", "avail", "capacity" will be incorrect/irrelevant to the corresponding file systems.
For example, the "capacity" field shows the percentage of the file system that is currently being used. When this issue occurs, this field may show the percentage as more than a million or so:
# df -k /space
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s7 140454588 18446744073709379423 139222236 13266262761034% /space

Или как я уже говорил - патчи

Спасибо. Проверю.