Warning: HTFS: bad dir inode 62730 on HTFS dev hd (1/42)
Hello all. I am receiving this message on the console of a SCO Openserver 5.0.7 server. The hardware is IBM, running mirrored SCSI drives with a hot-swap spare off of an IBM Serveraid controller. I suspect that some permutation of fsck can help me resolve whatever is causing the error, but I am not really sure how to proceed.
Would anyone be willing to share some of their knowledge with me?
Hi Friends . my linux try to start very slowly after give it this error:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root,
missing codepage or helper program, or other error
in some cases useful info is found in syslog - try
dmesg : tail or so
Kernel panic... (3 Replies)
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
I'm not sure exactly where to put this, so I'll just try here. I have an old SCO Openserver 5 box that has some important data on it. I had a hardware failure on the computer and can't boot from there. I obviously can't boot the drive from a different computer.
I tried to mount the HTFS filesystem... (6 Replies)
I have a 17GB SCSI disk in an SCO 5.0.6 server and it's running out of space because of a growing database on the disk. Consequently I would like to upgrade the 17GB to a 74GB disk and extend the partition.
First off, is partition extension available under HTFS - I know this is an old... (1 Reply)
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
# grep "Jul 3" syslog.messages | more
Jul 3 00:16:03 www3 CPU3: NOTICE: HTFS: No space on dev hd (1/42)
Jul 3 00:16:08 www3 CPU3: NOTICE: HTFS: No space on dev hd (1/42)
Jul 3 00:17:01 www3 CPU2: NOTICE: HTFS: No space on dev hd (1/42)
Jul 3 00:17:06 www3 syslogd: /usr/adm/debug: No space... (1 Reply)
HPSA(4) Linux Programmer's Manual HPSA(4)NAME
hpsa - HP Smart Array SCSI driver
SYNOPSIS
modprobe hpsa [ hpsa_allow_any=1 ]
DESCRIPTION
hpsa is a SCSI driver for HP Smart Array RAID controllers.
Options
hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not
explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of
operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that
would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4)
should still be used for these.
Supported hardware
The hpsa driver supports the following Smart Array boards:
Smart Array P700M
Smart Array P212
Smart Array P410
Smart Array P410i
Smart Array P411
Smart Array P812
Smart Array P712m
Smart Array P711m
StorageWorks P1210m
Configuration details
To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based
Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time.
FILES
Device nodes
Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the
SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively.
HPSA-specific host attribute files in /sys
/sys/class/scsi_host/host*/rescan
This is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g,.
hot-plugged tape drives, or newly configured or deleted logical drives, etc.) and notify the SCSI midlayer of any changes detected.
Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus,
for logical drive changes, the user should not normally have to use this attribute. This attribute may be useful when hot plugging
devices like tape drives, or entire storage boxes containing preconfigured logical drives.
/sys/class/scsi_host/host*/firmware_revision
This attribute contains the firmware version of the Smart Array.
For example:
# cd /sys/class/scsi_host/host4
# cat firmware_revision
7.14
HPSA-specific disk attribute files in /sys
/sys/class/scsi_disk/c:b:t:l/device/unique_id
This attribute contains a 32 hex-digit unique ID for each logical drive.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat unique_id
600508B1001044395355323037570F77
/sys/class/scsi_disk/c:b:t:l/device/raid_level
This attribute contains the RAID level of each logical drive.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat raid_level
RAID 0
/sys/class/scsi_disk/c:b:t:l/device/lunid
This attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed. c:b:t:l are
the controller, bus, target, and lun of the device.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat lunid
0x0000004000000000
Supported ioctl() operations
For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4) driver are
also supported by the hpsa driver. The data structures used by these ioctls are described in the Linux kernel source file
include/linux/cciss_ioctl.h.
CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the
same thing as writing to the hpsa-specific host "rescan" attribute.
CCISS_GETPCIINFO
Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).
CCISS_GETDRIVVER
Returns driver version in three bytes encoded as:
(major_version << 16) | (minor_version << 8) |
(subminor_version)
CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
Allows "BMIC" and "CISS" commands to be passed through to the Smart Array. These are used extensively by the HP Array Configuration
Utility, SNMP storage agents, and so on. See cciss_vol_status at <http://cciss.sf.net> for some examples.
SEE ALSO cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8),
<http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source
tree
Linux 2012-08-05 HPSA(4)