Hi,
when i execute a df, look what such a strange numbers appear
Does anybody know why these numbers appear??? is it critical?? is there a way to mend it?
df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d704 2033295 18446744073707800956 3722957 935292406453380% /dp_ixos
df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d704 1.9G 16384E 3.6G 935292406453380% /dp_ixos
thanks a lot for your help
regars
Pablo
First thing I'd do is unmount the filesystem and run fsck on it. I'd also run something like fdisk, cfdisk, or sfdisk to list the partition/slice layout for the physical disk. Ensure that the starting sector and lengths of each don't overlap. Be sure to read and understand the manual page for the fdisk like command you decide to use.
Depending on how you have your disk arranged, it is quite possible that when partitions/slices were defined, starting points were not correctly determined and data from a partition ahead of the one housing your odd filesystem has overwritten the filesystem in question, or you simply have a disk that's going bad.
Another clue would be any disk related messages in the system log.
ok i have found this in the system log
what do you think?
csi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 10:59:31 sv757 Corrupt label; wrong magic number
Jan 11 10:59:31 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 10:59:31 sv757 Corrupt label; wrong magic number
Jan 11 11:01:05 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:01:05 sv757 Corrupt label; wrong magic number
Jan 11 11:10:28 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:10:28 sv757 Corrupt label; wrong magic number
Jan 11 11:10:28 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:10:28 sv757 Corrupt label; wrong magic number
Jan 11 11:16:05 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:16:05 sv757 Corrupt label; wrong magic number
Jan 11 11:16:05 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:16:05 sv757 Corrupt label; wrong magic number
Jan 11 11:16:08 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:16:08 sv757 Corrupt label; wrong magic number
Jan 11 11:16:09 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:16:09 sv757 Corrupt label; wrong magic number
Jan 11 11:26:46 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:26:46 sv757 Corrupt label; wrong magic number
Jan 11 11:26:54 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:26:54 sv757 Corrupt label; wrong magic number
Jan 11 11:26:54 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:26:54 sv757 Corrupt label; wrong magic number
Jan 11 11:26:56 sv757 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6001438005dedd50000070000ae50000 (ssd53):
Jan 11 11:26:56 sv757 Corrupt label; wrong magic number
---------- Post updated at 07:15 PM ---------- Previous update was at 06:53 PM ----------
ok i will follow your first advice , that error doesnt have any to do with the issue.
so i give this thread as solved
thanks and regards
I'd say this is inconclusive. Could be a bad spot in a very unfortunate location (the partition/slice table), or could be poorly defined partition start/end points causing the corrupted partition to have been overwritten with data from the adjacent partition. You still need to look at output from an fdisk like tool to ensure that there isn't any overlap (if there is you've likely got much more corruption than what you've found). If there isn't overlap, then my guess would be a bad spot on the disk.
I'm not an expert when it comes to hard disk issues, maybe someone else with a bit more savvy will chime in and lend some help.