digz | 2 Aug 2005 12:27
Favicon

Re: WHY fdisk and df, /etc/fstab differ?

Can anyone explain this output what is ID ee and EFI GPT and how is ext2 or ext3 functioning under such a partitioning scheme and more how do i create new partitions on this hard-disk , this is RHEL3 on Itanium .

==============================================================================

> [root <at> advaitha /]# fdisk -l

>

> Disk /dev/sda: 146.8 GB, 146815737856 bytes

> 255 heads, 63 sectors/track, 17849 cylinders

> Units = cylinders of 16065 * 512 = 8225280 bytes

>

> Device Boot Start End Blocks Id System

> /dev/sda1 1 17850 143374743+ ee EFI GPT

>

> Disk /dev/sdb: 36.4 GB, 36420075520 bytes

> 255 heads, 63 sectors/track, 4427 cylinders

> Units = cylinders of 16065 * 512 = 8225280 bytes

>

> Device Boot Start End Blocks Id System

> /dev/sdb1 1 4428 35566479+ ee EFI GPT

>

> Disk /dev/sdc: 36.4 GB, 36420075520 bytes

> 255 heads, 63 sectors/track, 4427 cylinders

> Units = cylinders of 16065 * 512 = 8225280 bytes

>

> Device Boot Start End Blocks Id System

> /dev/sdc1 1 4428 35566479+ ee EFI GPT

=========================================================================================

> [root <at> advaitha /]# df -h

> Filesystem Size Used Avail Use% Mounted on

> /dev/sda5 9.9G 4.8G 4.6G 52% /

> /dev/sda3 100M 4.5M 96M 5% /boot/efi

> /dev/sda10 4.9G 214M 4.4G 5% /home

> /dev/sda4 20G 34M 19G 1% /opt

> none 997M 0 997M 0% /dev/shm

> /dev/sda9 4.9G 33M 4.6G 1% /tmp

> /dev/sda6 15G 2.0G 12G 15% /usr

> /dev/sda8 9.7G 242M 8.9G 3% /usr/local

> /dev/sda7 15G 8.1G 5.7G 59% /var

> /dev/cdrom 2.6G 2.6G 0 100% /mnt

=========================================================================================

> [root <at> advaitha /]# cat /etc/fstab

> LABEL=/ / ext3 defaults 1 1

> /dev/sda3 /boot/efi vfat defaults 0 0

> none /dev/pts devpts gid=5,mode=620 0 0

> LABEL=/home /home ext3 defaults 1 2

> LABEL=/opt /opt ext3 defaults 1 2

> none /proc proc defaults 0 0

> none /dev/shm tmpfs defaults 0 0

> LABEL=/tmp /tmp ext3 defaults 1 2

> LABEL=/usr /usr ext3 defaults 1 2

> LABEL=/usr/local /usr/local ext3 defaults 1 2

> LABEL=/var /var ext3 defaults 1 2

> /dev/sda11 swap swap defaults 0 0

> /dev/cdrom /mnt/cdrom udf,iso9660

> noauto,owner,kudzu,ro 0 0

=============================================================================================

[root <at> advaitha /]# cat /proc/mounts

rootfs / rootfs rw 0 0

/dev/root / ext3 rw 0 0

/proc /proc proc rw 0 0

none /dev/pts devpts rw 0 0

usbdevfs /proc/bus/usb usbdevfs rw 0 0

/dev/sda3 /boot/efi vfat rw 0 0

/dev/sda10 /home ext3 rw 0 0

/dev/sda4 /opt ext3 rw 0 0

none /dev/shm tmpfs rw 0 0

/dev/sda9 /tmp ext3 rw 0 0

/dev/sda6 /usr ext3 rw 0 0

/dev/sda8 /usr/local ext3 rw 0 0

/dev/sda7 /var ext3 rw 0 0

/dev/cdrom /mnt iso9660 ro 0 0

Thanks and Regards

Digz

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
Ext3-users mailing list
Ext3-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
evilninja | 2 Aug 2005 17:23
Picon

Re: WHY fdisk and df, /etc/fstab differ?


digz schrieb:
> 
> Can anyone explain this output what is ID ee and EFI GPT

% sfdisk -T | grep ^ee
ee  EFI GPT

So partition type "ee" stands for "EFI GPT".
Perhaps the Intel documentation is helpful:

http://developer.intel.com/technology/efi/

> and how is ext2 or 
> ext3 functioning under such a partitioning scheme and more how do i create 
> new partitions on this hard-disk , this is RHEL3 on  Itanium .

afaics creating partitions is done by fdisk & co as usual, EFI just sits
between the bootloader and the hardware/bios. the fs created on top of the
(special) partition shouldn't care about it.

Christian.
--
BOFH excuse #428:

Firmware update in the coffee machine
Markus Peuhkuri | 8 Aug 2005 14:57
Picon
Picon
Favicon

Re: Strange corruption (?) problem

Professor Stafylopaths wrote:

>Hello,
>
>I seem to have a strange problem with an ext3 fs partition.
>Whenever I transfer several files to this partition and compare
>the md5 and sha1 sums with the originals don't match. Seems like
>  
>
I would first suspect memory problem.  Run memtest86 to check your
system.  I had few years ago similar problem as I transfered lots of
files (that time large 18 GB disk).  Luckyly, before deleting original
files checked those with 'gzip -t' that failed...
Carlos Silva | 11 Aug 2005 00:58
Picon
Favicon

[BUG?] probable underflow on file date on ext2/3 filesystems

Hi guys,

        a user at Gentoo Bugzilla, reported that he archives files with
a
artificial timestamp of 1970-01-01 on an ext3 partition on his amd64
box. After remounting that partition, the file date becomes 2106-02-07.
I confirmed this bug and also tested it on several other partitions
(xfs, reiserfs) and they don't have this problem, just ext2 and ext3
have it. This problem also doesn't occur in x86, only on amd64 (as far
as i tested). If any more info is needed, just mail me.
The link to the bug is http://bugs.gentoo.org/101723

Carlos Silva
(cc me as i'm not on the ext2/3 lists)
kapil.sampath | 11 Aug 2005 10:56

URGENT: How to recover ext3 files?

Hi,

 

After panic boot, I have executed fsck for the mount point and we couldn’t find a single file. We have lot of directories under lost+found  like this #3194985.

 

Can anyone tell me how to recover the data from this folder? This is urgent.

 

Thanks in advance for your help.

 

Regards

Kapil Sampath

 

"Many of life's failures are people who did not realize how close they were to success when they gave up"

                                                                                                                                     - Thomas Edison

 

_______________________________________________
Ext3-users mailing list
Ext3-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
Damian Menscher | 11 Aug 2005 12:40
Picon

Re: URGENT: How to recover ext3 files?

On Thu, 11 Aug 2005, kapil.sampath <at> wipro.com wrote:

> After panic boot, I have executed fsck for the mount point and we
> couldn't find a single file. We have lot of directories under lost+found
> like this #3194985.
>
> Can anyone tell me how to recover the data from this folder? This is
> urgent.

I'm not sure I understand... are there files in those directories?  If 
so, then just move the directories out of lost+found, and give them 
reasonable names, and you're done.  This is what usually happens.

If the directories are all empty, then you have a much more serious 
problem.  Do you have backups?

Damian Menscher
--

-- 
-=#| Physics Grad Student & SysAdmin  <at>  U Illinois Urbana-Champaign |#=-
-=#| 488 LLP, 1110 W. Green St, Urbana, IL 61801 Ofc:(217)333-0038 |#=-
-=#| 4602 Beckman, VMIL/MS, Imaging Technology Group:(217)244-3074 |#=-
-=#| <menscher <at> uiuc.edu> www.uiuc.edu/~menscher/ Fax:(217)333-9819 |#=-
-=#| The above opinions are not necessarily those of my employers. |#=-
Stephen C. Tweedie | 11 Aug 2005 12:43
Picon
Favicon

Re: URGENT: How to recover ext3 files?

Hi,

On Thu, 2005-08-11 at 09:56, kapil.sampath <at> wipro.com wrote:

> After panic boot, I have executed fsck for the mount point and we
> couldn’t find a single file. We have lot of directories under
> lost+found  like this #3194985.

> Can anyone tell me how to recover the data from this folder? This is
> urgent.

It sounds like the root directory of your filesystem was lost.  What
happens then is that a new root and /lost+found directory will be
created, and all inodes in the system which could be found will have
been relinked into the new /lost+found.

So you'll have lost the names of a lot of files, but their contents may
still be intact.  And as long as the subdirectories under / were not
lost, they will also still be intact, so any files beneath them will
still have the correct filenames, in subdirs of /lost+found.

Basically you'll just have to go through the files and directories in
/lost+found renaming them back to their correct filenames.  That will
involve manually examining their contents to work out where in the
recreated root directory to rename them to.

Cheers,
 Stephen
Matt Bernstein | 19 Aug 2005 14:32
Picon
Favicon

Re: FSCK of corrupted ext3 filesystem

On May 23 Darryl Bond wrote:

> I have a 1.3TB ext3 filesystem that has been in service for about 3 months.
> About 6 days ago the Emulex fibrechannel controller logged a SCSI error and 
> the filesystem changed to RO.
> It appears that the filesystem instantly changes to RO and prevents the 
> journal from working, therefore invalidating the filesystem.
> The filesystem was unmounted and a remount was attempted. The mount failed due 
> to errors and an fsck came up with errors.
>
> Top output looks like this:
>
> PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 4562 root          25   0  780m   214m  236 R 99.9         42.6   6211:44 
> fsck.ext3

I'm seeing something rather similar, and not for the first time :-\

The MD layer failed a drive (on a 3ware Escalade card), but somehow the fs 
got wind of this and aborted the journal.

My fsck is on an Opteron, it's entirely CPU-bound, occupying about 1.4G of 
my 2G RAM, stuck in pass 2 six days in. My strace isn't picking up any 
calls.

My question is basically the same as Darryl's. How long do I give it?

(I did SIGKILL an earlier invocation as I hadn't passed the "-y" option.)

As my volume is all backup data, I'm willing to poke at it with debugfs if 
people on this list think it's worth a try. Maybe I can mark it as not 
having errors, and try to mount it? Or maybe there's a way of making fsck 
less thorough?

I don't like the idea of not having backups for more than a week. What I 
did last time this happened was to run mke2fs and start again from 
scratch. Can I do better this time?

Matt
Stephen C. Tweedie | 25 Aug 2005 13:29
Picon
Favicon

Re: FSCK of corrupted ext3 filesystem

Hi,

On Fri, 2005-08-19 at 13:32, Matt Bernstein wrote:

> My fsck is on an Opteron, it's entirely CPU-bound, occupying about 1.4G of 
> my 2G RAM, stuck in pass 2 six days in. My strace isn't picking up any 
> calls.
> 
> My question is basically the same as Darryl's. How long do I give it?

Which version of e2fsprogs?  There were some serious algorithmic
inefficiencies in some really old versions that could explain this sort
of thing.

--Stephen
Theodore Ts'o | 25 Aug 2005 18:16
Picon
Picon
Favicon
Gravatar

Re: FSCK of corrupted ext3 filesystem

On Thu, Aug 25, 2005 at 12:29:39PM +0100, Stephen C. Tweedie wrote:
> Hi,
> 
> On Fri, 2005-08-19 at 13:32, Matt Bernstein wrote:
> 
> > My fsck is on an Opteron, it's entirely CPU-bound, occupying about 1.4G of 
> > my 2G RAM, stuck in pass 2 six days in. My strace isn't picking up any 
> > calls.
> > 
> > My question is basically the same as Darryl's. How long do I give it?

What sort of messages was e2fsck printing beforehand?   

> Which version of e2fsprogs?  There were some serious algorithmic
> inefficiencies in some really old versions that could explain this sort
> of thing.

"Very old" here means version _before_ e2fsprogs 1.28 (released August
31, 2002).  So if you are using a distribution which is more than
three years old (in an industry where two years == infinity :-),
that's almost certainly the explanation.

						- Ted

Gmane