From: Andi Kleen <andi@firstfloor.org>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: Chris Wedgwood <cw@f00f.org>, nscott@aconex.com, xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Thu, 17 Jan 2008 02:25:00 +0100 [thread overview]
Message-ID: <p73ejchkzv7.fsf@bingen.suse.de> (raw)
In-Reply-To: <d711080c0801152325g3d57965dm92e3687a5f98c5f6@mail.gmail.com> (Gopala Krishna's message of "Wed\, 16 Jan 2008 12\:55\:17 +0530")
"Gopala Krishna" <gopalakrishna.n.m@gmail.com> writes:
> we need to get information about
> file like it's extent information and associated block numbers etc.
To
> extract these there is no system call
Actually there is the FIOBMAP ioctl for data blocks. e.g. it's used by
boot loaders like lilo to create a block map to read a file without
knowledge of the file system. Should work on all file systems that
support lilo.
It won't give you information about metadata blocks though.
-Andi
next prev parent reply other threads:[~2008-01-17 1:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 12:14 Question related to XFS sync , especially fsync Gopala Krishna
2008-01-14 12:24 ` Gopala Krishna
2008-01-14 12:25 ` Gopala Krishna
2008-01-14 14:06 ` Andi Kleen
2008-01-14 14:32 ` Olaf Frączyk
2008-01-14 14:43 ` ***** SUSPECTED SPAM ***** " Matthias Schniedermeyer
2008-01-14 17:55 ` Chris Wedgwood
2008-01-14 22:42 ` David Chinner
2008-01-15 13:44 ` Gopala Krishna
2008-01-15 15:18 ` Eric Sandeen
2008-01-15 22:26 ` Nathan Scott
2008-01-16 6:43 ` Gopala Krishna
[not found] ` <20080116064840.GA5725@puku.stupidest.org>
2008-01-16 7:25 ` Gopala Krishna
2008-01-16 7:52 ` Iustin Pop
2008-01-16 8:11 ` Gopala Krishna
2008-01-16 8:25 ` Christoph Hellwig
2008-01-16 9:00 ` Gopala Krishna
2008-01-16 11:52 ` Mark Goodwin
2008-01-16 21:17 ` Martin Steigerwald
2008-01-16 23:38 ` Mark Goodwin
2008-01-17 1:25 ` Andi Kleen [this message]
2008-01-17 2:44 ` David Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73ejchkzv7.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=cw@f00f.org \
--cc=gopalakrishna.n.m@gmail.com \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox