[Ocfs2-users] OCFS2: ERROR (device sdh1): ocfs2_direct_IO_get_blocks

[Daniel Keisling]

Patch was here:
http://oss.oracle.com/pipermail/ocfs2-devel/2008-September/002787.html

[root at wilracdbdr01 /]# debugfs.ocfs2 -R 'stat <23693699>' /dev/sdh1
        Inode: 23693699   Mode: 0660   Generation: 2707416418
(0xa15fe562)
        FS Generation: 236416663 (0xe176e97)
        Type: Regular   Attr: 0x0   Flags: Valid
        User: 503 (oracle)   Group: 505 (dba)   Size: 5120
        Links: 1   Clusters: 2
        ctime: 0x49a88566 -- Fri Feb 27 19:29:26 2009
        atime: 0x49a88566 -- Fri Feb 27 19:29:26 2009
        mtime: 0x49a88566 -- Fri Feb 27 19:29:26 2009
        dtime: 0x0 -- Wed Dec 31 19:00:00 1969
        ctime_nsec: 0x222d308b -- 573386891
        atime_nsec: 0x21390e2d -- 557387309
        mtime_nsec: 0x222d308b -- 573386891
        Last Extblk: 0
        Sub Alloc Slot: 0   Sub Alloc Bit: 19
        Tree Depth: 0   Count: 243   Next Free Rec: 1
        ## Offset        Clusters       Block#          Flags
        0  0             2              34610869        0x0

 [root at wilracdbdr01 /]# debugfs.ocfs2 -R stats /dev/sdh1
        Revision: 0.90
        Mount Count: 0   Max Mount Count: 20
        State: 0   Errors: 0
        Check Interval: 0   Last Check: Fri Feb 27 19:47:46 2009
        Creator OS: 0
        Feature Compat: 1 BackupSuper
        Feature Incompat: 0 None
        Tunefs Incomplete: 0 None
        Feature RO compat: 0 None
        Root Blknum: 5   System Dir Blknum: 6
        First Cluster Group Blknum: 3
        Block Size Bits: 12   Cluster Size Bits: 12
        Max Node Slots: 4
        Label: ph1p_arch
        UUID: 839B5D0925C74CD4920F4E8CC065D180
        Cluster stack: classic o2cb
        Inode: 2   Mode: 00   Generation: 236416663 (0xe176e97)
        FS Generation: 236416663 (0xe176e97)
        Type: Unknown   Attr: 0x0   Flags: Valid System Superblock
        User: 0 (root)   Group: 0 (root)   Size: 0
        Links: 0   Clusters: 39321087
        ctime: 0x48515d46 -- Thu Jun 12 13:30:46 2008
        atime: 0x0 -- Wed Dec 31 19:00:00 1969
        mtime: 0x48515d46 -- Thu Jun 12 13:30:46 2008
        dtime: 0x0 -- Wed Dec 31 19:00:00 1969
        ctime_nsec: 0x00000000 -- 0
        atime_nsec: 0x00000000 -- 0
        mtime_nsec: 0x00000000 -- 0
        Last Extblk: 0
        Sub Alloc Slot: Global   Sub Alloc Bit: 65535

> -----Original Message-----
> From: Joel Becker [mailto:Joel.Becker at oracle.com] 
> Sent: Friday, February 27, 2009 6:50 PM
> To: Daniel Keisling
> Cc: ocfs2-users at oss.oracle.com; Sunil Mushran
> Subject: Re: OCFS2: ERROR (device sdh1): ocfs2_direct_IO_get_blocks
> 
> On Fri, Feb 27, 2009 at 06:40:38PM -0600, Daniel Keisling wrote:
> > I'm am getting the following error when writing to an OCF2 
> filesystem:
> >  
> >  
> > Feb 27 19:06:37 wilracdbdr01 kernel: OCFS2: ERROR (device sdh1):
> > ocfs2_direct_IO_get_blocks: Inode 23693699 has a hole at block 6
> > Feb 27 19:06:37 wilracdbdr01 kernel: File system is now 
> read-only due to
> > the potential of on-disk corruption. Please run fsck.ocfs2 
> once the file
> > system is unmounted.
> 
> 	This basically says that your filesystem does not support sparse
> files, but it does have a hole in an inode - which shouldn't happen if
> sparse isn't supported.
> 	Can you send the output of "debugfs.ocfs2 -R 'stat <23693699>'
> /dev/sdh1" and "debugfs.ocfs2 -R stats /dev/sdh1"?
> 
> > I saw a patch that was released in September 2008.  How do 
> I get this?
> 
> 	What patch?  Do you have a link?  Without knowing the patch I
> can't tell you whether that patch affects you.
> 
> > This a production system and we are currently unable to 
> start the DB.
> 
> 	If you have the appropriate support, you should call support and
> file that way.  Support will also want the information I requested
> above.
> 
> Joel
> -- 
> 
> "Three o'clock is always too late or too early for anything you
>  want to do."
>         - Jean-Paul Sartre
> 
> Joel Becker
> Principal Software Developer
> Oracle
> E-mail: joel.becker at oracle.com
> Phone: (650) 506-8127
> 
> 

______________________________________________________________________
This email transmission and any documents, files or previous email
messages attached to it may contain information that is confidential or
legally privileged. If you are not the intended recipient or a person
responsible for delivering this transmission to the intended recipient,
you are hereby notified that you must not read this transmission and
that any disclosure, copying, printing, distribution or use of this
transmission is strictly prohibited. If you have received this transmission
in error, please immediately notify the sender by telephone or return email
and delete the original transmission and its attachments without reading
or saving in any manner.