I have NetApp LUN that was presented to a Red Hat Enterprise Linux Server release 5.7 (Tikanga) machine.
But this LUN has already data, because it was being used on another server.
I can see the new LUN when running fdisk:
so I think the new LUN is /dev/sda
But how do I go about mounting as a file system?
I cannot make a file system on it... because there is data already on it...
I have a file --> file1.txt
i need to copy this file to another server using FTP....the 2 servers are server1 and server2..may i know how to write a script that can do this?
thanks in advance! Im a newbie to this... (4 Replies)
I just moved a dedicated server, which included moving to a new subnet, and new IP address. Now my server is not reconnecting - I've tried ifconfig, altering the etc/hosts file with the new ip address, with no luck. (5 Replies)
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Hi All,
I am new for this blog and this is my first Query on this blog. I would like to dael with graet masters on linux.
Here we go,
After storage people created the LUN, How to add that LUN to Linux server. (Make that LUN visibility on linux server.) ?
How to view the LUN... (5 Replies)
Hi,
I have compiled FreeTDS on AIX 5.3. Its my dev environment so I have c compilers on the box so I was able to compile. From the test environment onwards I will not be able to have c compilers. I tried to move these files directly to the test environment with the same directory structure but I... (2 Replies)
Hi,
I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is :
node 1 shows the shared iscsi lun as sdc
node 2 shows the same as sdg (changes on reboots)
Due to this (i guess) i get i/o error & i can not read files created by... (0 Replies)
I have created a lun on Storage and connected it to server using fiber channel.
LUN is presented on new Server .
How do i check and mount this newly created LUN? (1 Reply)
Discussion started by: pinga123
1 Replies
9. Post Here to Contact Site Administrators and Moderators
SD(4) Linux Programmer's Manual SD(4)NAME
sd - Driver for SCSI Disk Drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIG
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a re-read of the SCSI disk partition tables. No parameter is needed.
The scsi(4) ioctls are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl() will return -EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
SEE ALSO scsi(4)
1992-12-17 SD(4)