<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Stan, do you check dates on links before you paste them here? I don't care if its the 1st results of the google search 'meaning of life', its irrelevant and oudated.<br><br>> From: xfs-request@oss.sgi.com<br>> Subject: xfs Digest, Vol 29, Issue 102<br>> To: xfs@oss.sgi.com<br>> Date: Sun, 30 Jan 2011 21:49:14 -0600<br>> <br>> Send xfs mailing list submissions to<br>> xfs@oss.sgi.com<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://oss.sgi.com/mailman/listinfo/xfs<br>> or, via email, send a message with subject or body 'help' to<br>> xfs-request@oss.sgi.com<br>> <br>> You can reach the person managing the list at<br>> xfs-owner@oss.sgi.com<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of xfs digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. RE: xfs Digest, Vol 29, Issue 101 (lord worm)<br>> 2. Re: xfs Digest, Vol 29, Issue 101 (Stan Hoeppner)<br>> 3. Re: [patch] xfsprogs: repair pagefault due to missed out<br>> sanity NULL check (Ajeet Yadav)<br>> 4. Re: [patch] xfsprogs: repair never return if device removed<br>> (Ajeet Yadav)<br>> 5. Re: how to decode metadump info produced by xfs_db, and<br>> superblock error (Dave Chinner)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Sun, 30 Jan 2011 13:27:51 -0500<br>> From: lord worm <cryptopsy@live.com><br>> Subject: RE: xfs Digest, Vol 29, Issue 101<br>> To: <xfs@oss.sgi.com><br>> Message-ID: <SNT130-w7320373265265D515EDD5DAE30@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> <br>> Stan I have no idea, could you tell me in detail why dd failed, and what exactly those restore commands provide specifically?<br>> <br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://oss.sgi.com/pipermail/xfs/attachments/20110130/dee98fcc/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sun, 30 Jan 2011 15:03:42 -0600<br>> From: Stan Hoeppner <stan@hardwarefreak.com><br>> Subject: Re: xfs Digest, Vol 29, Issue 101<br>> To: xfs@oss.sgi.com<br>> Message-ID: <4D45D22E.2060603@hardwarefreak.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> lord worm put forth on 1/30/2011 12:27 PM:<br>> > <br>> > Stan I have no idea, could you tell me in detail why dd failed, and what exactly those restore commands provide specifically?<br>> <br>> This might have some relevance. 2nd hit Googling for "dd with xfs":<br>> <br>> http://oss.sgi.com/archives/xfs/2003-04/msg00802.html<br>> <br>> -- <br>> Stan<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Mon, 31 Jan 2011 11:39:15 +0900<br>> From: Ajeet Yadav <ajeet.yadav.77@gmail.com><br>> Subject: Re: [patch] xfsprogs: repair pagefault due to missed out<br>> sanity NULL check<br>> To: xfs@oss.sgi.com<br>> Message-ID:<br>> <AANLkTinK25hL3Ljy42S6KrqEJ7nW_L+c77GPJhBVo=58@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> I did not receive any response / review comment on solution patch I sent.<br>> <br>> diff -Nurp xfsprogs/repair/dir2.c xfsprogs-dirty/repair/dir2.c<br>> <br>> --- xfsprogs/repair/dir2.c 2010-07-16 13:07:09.000000000 +0900<br>> <br>> +++ xfsprogs-dirty/repair/dir2.c 2011-01-28 18:49:21.000000000 +0900<br>> <br>> @@ -110,9 +110,10 @@ da_read_buf(<br>> <br>> bplist[i] = libxfs_readbuf(mp->m_dev,<br>> <br>> XFS_FSB_TO_DADDR(mp, bmp[i].startblock),<br>> <br>> XFS_FSB_TO_BB(mp, bmp[i].blockcount), 0);<br>> <br>> - if (!bplist[i])<br>> <br>> + if (!bplist[i]){<br>> <br>> + nex = i;<br>> <br>> goto failed;<br>> <br>> -<br>> <br>> + }<br>> <br>> pftrace("readbuf %p (%llu, %d)", bplist[i],<br>> <br>> (long long)XFS_BUF_ADDR(bplist[i]),<br>> <br>> XFS_BUF_COUNT(bplist[i]));<br>> On Fri, Jan 28, 2011 at 8:13 PM, Ajeet Yadav <ajeet.yadav.77@gmail.com>wrote:<br>> <br>> > libxfs_putbuf() is called with bp = NULL, resulting in pagefault in<br>> > libpthread.<br>> ><br>> > Function da_read_buf() allocate array of xfs_buf_t *<br>> ><br>> > * xfs_buf_t **bplist;*<br>> ><br>> > * bplist = calloc(nex, sizeof(*bplist));*<br>> ><br>> > Read and fill it using<br>> ><br>> > *for (i = 0; i < nex; i++) {<br>> > bplist[i] = libxfs_readbuf()*<br>> ><br>> > * if (!bplist[i]){<br>> > goto failed;<br>> > } *<br>> ><br>> > *}*<br>> ><br>> > *failed:<br>> > for (i = 0; i < nex; i++)<br>> > libxfs_putbuf(bplist[i]);*<br>> ><br>> > Now assume nex = 10,<br>> ><br>> > 1. Will create bplist for 10 array elements.<br>> ><br>> > 3. Reading from disk 0,1, 2, 3<br>> ><br>> > 4. When reading from disk 4, USB is removed<br>> ><br>> > 5. libxfs_readbuf() will at fail, pblist[4] = NULL, goto failed.<br>> ><br>> > 6. Since only 4 buffers were read successfully, so only 4 are in lock<br>> > state.<br>> ><br>> > 7. Error handling will unlock buffer from 1-10<br>> ><br>> > 8. Buffer 0-3 were read successfully, hence will have valid pdlist[i]<br>> ><br>> > 9. Access pblist[4] == NULL, therefore unlocking will set bp == NULL in<br>> > libxfs_putbuf(bp);<br>> > 10. Page fault in libpthread<br>> ><br>> ><br>> > Solution patch attached with mail<br>> ><br>> ><br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://oss.sgi.com/pipermail/xfs/attachments/20110131/4e2718ae/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Mon, 31 Jan 2011 11:41:16 +0900<br>> From: Ajeet Yadav <ajeet.yadav.77@gmail.com><br>> Subject: Re: [patch] xfsprogs: repair never return if device removed<br>> To: xfs@oss.sgi.com<br>> Message-ID:<br>> <AANLkTikyOfkbtxN3Et5YZRJ2rPpdsVouJkyRW4fDbUG7@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> I did not receive and response / reviews on patch.<br>> <br>> diff -Nurp xfsprogs/repair/sb.c xfsprogs-dirty/repair/sb.c<br>> <br>> --- xfsprogs/repair/sb.c 2011-01-28 20:23:02.000000000 +0900<br>> <br>> +++ xfsprogs-dirty/repair/sb.c 2011-01-28 20:21:06.000000000 +0900<br>> <br>> @@ -122,8 +122,9 @@ find_secondary_sb(xfs_sb_t *rsb)<br>> <br>> done = 1;<br>> <br>> }<br>> <br>> - if (!done && (bsize = read(x.dfd, sb, BSIZE)) == 0) {<br>> <br>> + if (!done && (bsize = read(x.dfd, sb, BSIZE)) <= 0) {<br>> <br>> done = 1;<br>> <br>> + do_warn(_("Couldn't find candidate secondary superblock, exiting...\n"));<br>> <br>> }<br>> <br>> do_warn(".");<br>> <br>> On Fri, Jan 28, 2011 at 8:31 PM, Ajeet Yadav <ajeet.yadav.77@gmail.com>wrote:<br>> <br>> > xfsprogs all version, delete primary superblock of xfs partition<br>> ><br>> > dd if=/dev/zero of=/dev/sda1 bs=512 count=1<br>> > sync<br>> ><br>> > Run xfs_repair in partition, while its searching for secondary superblock,<br>> > remove the disk (USB) xfs_repair will never exit and will loop in never<br>> > ending ............<br>> ><br>> > Please find patch attached with mail<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://oss.sgi.com/pipermail/xfs/attachments/20110131/77ad227f/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Mon, 31 Jan 2011 14:51:31 +1100<br>> From: Dave Chinner <david@fromorbit.com><br>> Subject: Re: how to decode metadump info produced by xfs_db, and<br>> superblock error<br>> To: lord worm <cryptopsy@live.com><br>> Cc: xfs@oss.sgi.com<br>> Message-ID: <20110131035131.GI21311@dastard><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> On Sun, Jan 30, 2011 at 08:21:19PM -0500, lord worm wrote:<br>> > > Date: Mon, 31 Jan 2011 08:40:26 +1100<br>> > > From: david@fromorbit.com<br>> > > To: cryptopsy@live.com<br>> > > Subject: Re: how to decode metadump info produced by xfs_db, and superblock error<br>> > > <br>> > > On Sun, Jan 30, 2011 at 11:33:53AM -0500, lord worm wrote:<br>> > > > > Date: Sun, 30 Jan 2011 18:16:30 +1100<br>> > > > > From: david@fromorbit.com<br>> > > > > To: cryptopsy@live.com<br>> > > > > CC: xfs@oss.sgi.com<br>> > > > > Subject: Re: how to decode metadump info produced by xfs_db, and superblock error<br>> > > > > <br>> > > > > On Sat, Jan 29, 2011 at 07:25:10PM -0500, lord worm wrote:<br>> > > > > > <br>> > > > > > What kind of information is in this file produced by metadump, is it worth reading it somehow?<br>> > > > > > <br>> > > > > > I'm trying to first understand what's causing a 'superblock cannot<br>> > > > > > be read' error in my XFS after a succesfully dd of the partition<br>> > > > > > (dd succeeds in copying to a file, and also restoring, but after<br>> > > > > > restoring it cannot mount).<br>> > > > > <br>> > > > > dmesg output when the mount fails?<br>> > > > <br>> > > > Could you email the mailing list next time as well, so that my<br>> > > > forwards are directed towards everyone, please?<br>> > > <br>> > > I did:<br>> > > <br>> > > http://oss.sgi.com/archives/xfs/2011-01/msg00486.html<br>> > > <br>> > > As for list ettiquette - please don't top post and wrap all you text<br>> > > except for code and pasted log messages at 72 columns.....<br>> <br>> Fixed that for you again.<br>> <br>> > > > Here's dmesg from the backup file, but I don't have it from the original disk after restoring it:<br>> > > > <br>> > > > [ 362.685464] attempt to access beyond end of device<br>> > > > [ 362.685468] loop5: rw=0, want=15662872, limit=15661056<br>> > > > [ 362.685473] I/O error in filesystem ("loop5") meta-data dev loop5 block 0xeeff17 ("xfs_read_buf") error 5 buf count 512<br>> > > > [ 362.685478] XFS: size check 2 failed<br>> > > <br>> > > Simple problem - you copied the filesystem back onto a device that<br>> > > is too small for the filesystem.<br>> > <br>> > When I reply to this email, it defaults to david@fromorbit.com, so<br>> > how will the others see it?<br>> <br>> Reply to all. It's common courtesy to reply to everyone on the<br>> cc-list for mailing list traffic as it often contains people not<br>> subscribed to the mailing list (e.g. a person reporting a bug).<br>> <br>> I've added the xfs list back onto the cc-list.<br>> <br>> > I can't mount the direct dd image of the drive as a loop device<br>> > either by the same error.<br>> <br>> Which means you probably didn't copy the entire drive in the first<br>> place.<br>> <br>> > The error persists even when its not<br>> > the filesystem that was copied back onto the device. Additionally,<br>> > its the exact same device with the exact same partition type<br>> > created by the exact same version of disk.<br>> <br>> partition type doesn't matter - the size does. The above error<br>> indicates that the loop device is 1816 sectors (908kiB) shorter than<br>> it needs to be, so maybe you aren't recreating the partition as<br>> large as it needs to be, too....<br>> <br>> As it is, the question I have at this point is why are you trying to<br>> copy the filesystem via dd? if all you want is an image, xfs_copy is<br>> probably what you want....<br>> <br>> Cheers,<br>> <br>> Dave.<br>> -- <br>> Dave Chinner<br>> david@fromorbit.com<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> xfs mailing list<br>> xfs@oss.sgi.com<br>> http://oss.sgi.com/mailman/listinfo/xfs<br>> <br>> <br>> End of xfs Digest, Vol 29, Issue 102<br>> ************************************<br> </body>
</html>