Since I am not a linux admin, I will give you the point of vue of a pure unix admin..
looks like a disk physically partitionned in 3 not fully LVM compliant (like HP-UX 9...) and so would see one file system for booting the second for swap and the third (all the disk left), dedicated to LVM (this is about /dev/sda*...)
It is difficult to say more since we have no idea what hardware is installed...
A "hard disk" is (classically - the logic is still used even if it doesn't look like that any more) a stack of rotating platters mounted on a common spindle. On these platters there are concentric rings ("tracks") of magnetic coating. These concentric rings are divided in "sectors".
As the spindle is rotating a device goes in between the platters which looks like a comb, carrying a read/write head on every tip.
The output now tells you the geometry of this disk - at least, as it is told by the disk device to the controller: it has 255 heads, meaning there are are 128 such platters. (Every platter has a lower and an upper side to read from and has 2 [read-write-] heads therefore.)
There are 6527 concentric tracks (=cylinders) on every disk. Because the corresponding tracks on all the platters build a logical unit it is easy to see why this is called a "cylinder".
Lastly, every such track is divided into 63 sectors. Note that sectors occupy a certain angle rather than a certain area of magnetic material. The inner sectors are therefore shorter than the outer sectors, but still can carry the same amount of data. This is the reason why every track is divided into the same number of sectors.
Quote:
Originally Posted by stunn3r
This is the disk device itself. "/dev/sda" means the whole disk, while "/dev/sda<n>" means "a certain partition number <n> on /dev/sda"
Quote:
Originally Posted by stunn3r
The partition table layout for the first disk. Probably this is a Linux system disk and Linux can't boot from LVM volumes. Therefore a single partition "/dev/sda1" to boot from, probably mounted at "/boot" and containing the boot loader (Grub?). Than a partition "/dev/sda2", which contains a swap partition. It is possible to have swap partitions inside the LVM, but some Linux admins hold that it is better to have the swap outside LVM too. Finally a LVM partition, which contains all the other volumes/filesystems there are in the system.
Quote:
Originally Posted by stunn3r
The second disk /dev/sdb. It seems not to carry any partitions at all yet. Similar for all the other disks in your system.
The disk "/dev/sdf" has a size of 290GB, that part should be obvious.
The other disk "/dev/sdh" was not yet partitioned. A disk drive has to be written with some low-level information prior to be used by an operating system. This is the "partitioning" first, which divides the disk in one or more logical "disks" - partitions. Only after partitioning these logical disks can be used to store filesystems on them. Storing the file system information is called "formatting".
Think of a disk like a bare storage room: to actually store something in it you first have to build some shelves, on which to store the goods you want to store, probably prepare a list where you can enter all the things you stored and the place they are at to find them again, etc.. Formatting is like building these shelves and the list. It is preparing the storage room for actually storing goods there.
Hi All,
When can we see these messages in the syslog.
We have service guard cluster software installed on hpux 11iv3 servers.
We were able to see the below error so many times in our syslog messages
cmdisklockd: Unable to convert device to I/O tree node: I/O tree node does not exist.
... (2 Replies)
Hello,
MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk:
Partition table created on linux (centos 6.3):
# fdisk -l /dev/sdc
Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 *... (2 Replies)
Hi all,
I'm working with a peice of software that runs on Linux that allows planning trips in cars through maps. This software has different variations depending on the type of car, e.g. BMW, Audi, Hyundai, etc... Each variation has a dependency on common external components that are not... (1 Reply)
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc 10... (4 Replies)
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc... (1 Reply)
Hello there,
i am trying to write a shell script to analyse some of my log files.
I want the script to check if there is a logfile from yesterday or today (some times the script that creates the logfile takes a bit longer and its after 00:00) and search the logfile itself if the script was... (0 Replies)
Hi,
Recently I faced with need of analyze root disk. I figured out two possible ways to do it:
1. Practical. Boot from CD and run format
2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format.
I've already... (3 Replies)
hi you all!
I can write a network program to send and receive some messages. I use
read() and write() functions for extracting of sending messages via a given socket. By doing so, i know only the actions performed at the application layer of the TCP/IP suite. But i want to control the actual... (2 Replies)
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)