At 23:20:39 on Thursday Thursday 18 November 2010, David Haller <dnh@opensuse.org> wrote:
Hello,
On Thu, 18 Nov 2010, Stan Goodman wrote:
At 02:20:32 on Thursday Thursday 18 November 2010, David Haller
<dnh@opensuse.org> wrote:
On Tue, 16 Nov 2010, Stan Goodman wrote:
After fsck finishes, its report includes (these are numbers from a few days ago): "/dev/sda7/:21727/2564096 files (0.7% non-contiguous 1982750/10241429 blocks".
[..]
You can find out how large your blocks are (and a lot more) by using: tune2fs -l /dev/sda7
***** # tune2fs -l /dev/sda7 Errors behavior: Continue
I like to use 'remount-ro' here. That way I have a chance to notice problems. Use 'tune2fs -e remount-ro /dev/sda7' to adjust (see 'man tune2fs').
Filesystem OS type: Linux Inode count: 2564096
Second number from the first group (number of files)
Block count: 10241429
Second number from the second group (number of blocks)
Free blocks: 8254037
10241429 - 8254037 = 1987392 (number of used blocks)
Free inodes: 2541547
2564096 - 2541547 = 22549
Block size: 4096
For use with 'df -B'.
Filesystem created: Mon Sep 13 22:40:36 2010 Last mount time: Sun Jul 4 03:00:08 2010 Last write time: Sun Jul 4 03:00:08 2010 Mount count: 1 Maximum mount count: -1 Last checked: Sun Jul 4 03:01:09 2010
[..]
Interesting that the file system was most recently mounted and written two months before it was created.
Is your time set correctly? Or more specifically: the hwclock in the BIOS? I'm not sure at what time that is read to the system-time during boot.
No, it isn't, as I have mentioned some time ago. When normal booting fails, the BIOS time is displayed (along with a notice that it is wrong) as 2002/1/12. When the system is up, the time is correctly displayed because NTS has corrected it.
But I do not see that it is running out of inodes (under 1%) or blocks (20%); why is it complaining?
It is not. It's just an informational status message at the end of any fsck.
smartctl -s on /dev/sda smartctl -A /dev/sda
***** # smartctl -A /dev/sda
1 Raw_Read_Error_Rate 226329685
That's usually nothing to worry about, depends on the drive though. Some drives raise that in normal operations, more or less continuously. Other drives usually have this staying at 0.
5 Reallocated_Sector_Ct 0
ok.
7 Seek_Error_Rate 3056198
Also depending on the drive. I see this being "high" with the 2 Seagates, and not with the Samsungs.
10 Spin_Retry_Count 0
Ok (not bad blocks related, but mechanical).
183 Runtime_Bad_Block 0 184 End-to-End_Error 0 187 Reported_Uncorrect 0
ok.
195 Hardware_ECC_Recovered 226329685
Usually nothing to worry about (depends on the drive).
197 Current_Pending_Sector 0 198 Offline_Uncorrectable 0
Ok (those and Nr. 5 above are the "bad blocks" relevant ;)
240 Head_Flying_Hours 32388348382196
Obviously bogus.
It antedates the Big Bang.
196 is missing from the output.
It's drive dependant. Probably equivalent to 183 or 187.
See http://en.wikipedia.org/wiki/S.M.A.R.T#ATA_S.M.A.R.T._attributes
If I am reading this correctly, the disk is on its last legs. This is not an old disk (less than a year, much less than I remembered). Am I misinterpreting it?
Yes. The disk is probably fine. You might want to run 'smartd' though to have an eye on the disk (in this box, I have only one drive with similar high numbers (with Attributes 1, 7 or 195), and that one also has some bad sectors, but AFAIR I have some drives in the other box, that have similar numbers as you and those drives are fine).
HTH, -dnh
I can't see a conspicuous evolutionary advantage in being good at higher mathematics. -- James Riden
Why... That would imply that rock singers and basketball players would have more reproductive opportunities than mathematicians! Impossible to believe. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org