Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From past couple of days I am facing problem on my Linux server RHEL 5.3 x64.
there is a volume from storage about 7TB formatted as ext3 was being in use, but from last week I am getting error when I was trying to create a new file/directory.
there wasn't any changes on server or software as far as I remember, the device name was /dev/sda1 and volume was created by parted and labeled as gpt.
after reboot I was unable to mount it as /dev/sda1 the list the volume and came to know that there is new device
Code:
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: The size of this disk is 7.7 TB (7696581394432 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
partition table format (GPT).
Disk /dev/sda: 7696.5 GB, 7696581394432 bytes
255 heads, 63 sectors/track, 935722 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 267350 2147483647+ ee EFI GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/dm-0'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: The size of this disk is 7.7 TB (7696581394432 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
partition table format (GPT).
Disk /dev/dm-0: 7696.5 GB, 7696581394432 bytes
255 heads, 63 sectors/track, 935722 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-0p1 1 267350 2147483647+ ee EFI GPT
then I mount it as /dev/dm-1 it worked fine , but on software being use this volume is not working since that day.
Just now I have added a new disk from same storage as /dev/sdb and created a new gpt volume. After creating and then I was formatting by mkfs.ext3 it return the error,
Code:
# mkfs.ext3 -j /dev/sdb1
mke2fs 1.39 (29-May-2006)
/dev/sdb1 is apparently in use by the system; will not make a filesystem here!
Hello,
From past couple of days I am facing problem on my Linux server RHEL 5.3 x64. there is a volume from storage about 7TB formatted as ext3 was being in use, but from last week I am getting error when I was trying to create a new file/directory.
there wasn't any changes on server or software as far as I remember, the device name was /dev/sda1 and volume was created by parted and labeled as gpt.
Well, quite obviously SOMETHING CHANGED, otherwise your system would be just as it had been. Things like disks relabeling themselves don't just 'happen'....what was done? After working with Linux now for NINE YEARS, you should have some idea of what's going on with your systems. Without knowing what happened, there's no way we can tell you WHY it happened, or what to 'undo'.
Quote:
after reboot I was unable to mount it as /dev/sda1 the list the volume and came to know that there is new device then I mount it as /dev/dm-1 it worked fine , but on software being use this volume is not working since that day.
Would help if you told us WHAT 'software' is not working, and what the message(s) are.
Quote:
Just now I have added a new disk from same storage as /dev/sdb and created a new gpt volume. After creating and then I was formatting by mkfs.ext3 it return the error,
Can any help on this issue.
Obviously there is already a running filesystem mounted on /dev/sdb1. So make the file system on the correct device.
Also, since you're running RHEL, have you contacted Red Hat?? You are PAYING for RHEL, right?? So that entitles you to support. RHEL5.3 is VERY old too, and I don't think it's even supported any longer. Upgrading would be a good thing.
I have deleted the /etc/multipath.conf and disabled the multipathd at startup after this reboot the server. now I can format the new disk LUN and also the old disk can be mount as /dev/sda1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.