| To: | nscott@xxxxxxxxxx |
|---|---|
| Subject: | Re: Question related to XFS sync , especially fsync |
| From: | "Gopala Krishna" <gopalakrishna.n.m@xxxxxxxxx> |
| Date: | Wed, 16 Jan 2008 12:13:54 +0530 |
| Cc: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=2t3n6AQTQ+6Qcr+tj0+oiJOE5/nHBbKZP1p31BQ3Pvc=; b=uvk4sAhE+3ZlS875fjDPzpLLe78CjjQtG7RIDglUIewetJ4wWbizEFx/8onJZlNMuBK4t5gTNW+cxT1eVGCY0u4yF2r4NL4CYGc5GMbX1ToaUpmDKIgy+6ITOihtU6zYwPNzhwXF4LicKuehYU44eYhsznm4riKnz/a2DSzrIhU= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=RyHob+mqyaBcoZ4xsBNgRvDfMymfTT30xEZ0gOocnObQqWYeBSffW32/qE2uDprGqXHDWrfVYfbkWNekJEWI2s/m/x3wkm9V+t/aL+g5apomR1o4kMAG/s4czqm3WnE7XIFEr1Ku+jJJbun6TMmH/O2s9auItKz3B4l18lSi5xc= |
| In-reply-to: | <1200436012.9463.184.camel@edge.scott.net.au> |
| References: | <d711080c0801140414n48e47140y88f545eba605eff9@mail.gmail.com> <20080114224245.GT155259@sgi.com> <d711080c0801150544i53d7abb2hbea659116ce0006b@mail.gmail.com> <478CCEAC.9010008@sandeen.net> <1200436012.9463.184.camel@edge.scott.net.au> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Is there any XFS call from user level to flush metadata for a given file or complete log to disk? Thanks, Gopal. On 1/16/08, Nathan Scott <nscott@xxxxxxxxxx> wrote: > > On Tue, 2008-01-15 at 09:18 -0600, Eric Sandeen wrote: > > > > > I have lot of code getting in to that. To explain that I have to go > > through > > > that complex part of the code to explain in detail. > > > > > > Basically once we get indoe number for a given file from the > > available > > > system call, we only depending upon the XFS layout and it's > > structure. We > > > are reading super block from a particular disk offset and > > calculating > > > address for inode offset and its address on the disk and reading > > directly > > > from the disk offset. We are totally depending on XFS on disk > > layout. > > > > Can I ask why you are doing this? :) > > > > This would be good to know. If you absolutely must use inode numbers > instead of path names, you should use the "by-handle" interface (like > xfsdump, xfs_fsr, etc) and not use the ondisk structures directly - > doing so is always "broken by design" and you'll get little sympathy > here for doing so. :) > > cheers. > > -- > Nathan > > [[HTML alternate version deleted]] |
| Previous by Date: | Re: [REVIEW] Refactor xfs_repair's process_dinode_int, Christoph Hellwig |
|---|---|
| Next by Date: | Re: Question related to XFS sync , especially fsync, Gopala Krishna |
| Previous by Thread: | Re: Question related to XFS sync , especially fsync, Nathan Scott |
| Next by Thread: | Re: Question related to XFS sync , especially fsync, Gopala Krishna |
| Indexes: | [Date] [Thread] [Top] [All Lists] |