<div>Hi,</div>
<div> </div>
<div>There seems to be a problem in posting - I already apologized and provided complete details. I guess this was the first time, i missed on providing the test case.</div>
<div> </div>
<div>Please refer my earlier post on the same issue:</div>
<div> </div>
<div> </div>
<div>Extremely sorry for inconvenience, will take care about posting complete details in future.<br> <br>Test Case : <br>cp Complex directory structure(large no of files and directories) to my XFS formatted partition:<br>
cp -ar /LibExe /usb/sda2<br>Unplug the USB while the COPY is in progress.<br> <br>Storage: USB Flash, USB HDD (Both)<br> <br>Kernel: 2.6.34<br>Target: MIPS<br>LOGS:<br>usb 2-1: USB disconnect, address 7<br>Device sda2, XFS metadata write error block 0x0 in sda2<br>
xfs_force_shutdown(sda2,0x1) called from line 1004 of file fs/xfs/linux-2.6/xfs_buf.c. Return address = 0x801cc294<br>Filesystem "sda2": I/O Error Detected. Shutting down filesystem: sda2<br>Please umount the filesystem, and rectify the problem(s)<br>
<br>Plug in USB Port1<br>sd 7:0:0:0: [sdb] Attached SCSI disk<br>Filesystem "sda2": xfs_log_force: error 5 returned.<br>Filesystem "sda2": xfs_log_force: error 5 returned.<br>Filesystem "sda2": xfs_log_force: error 5 returned.<br>
Filesystem "sda2": xfs_log_force: error 5 returned.<br>- Show quoted text -<br>INFO: task usb_mount:1858 blocked for more than 120 seconds.<br>"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br>
usb_mount D [84a42440] 8032d62c 0 1858 1816 (user thread)<br>Stack : 00000107 00000000 85e7be80 00030002 84a425c8 8032d62c 7fffffff 84a42440<br> 00000002 8496e200 00000001 00000000 85e7bf00 85e7bef8 7fa2f2e0 8032d62c<br>
00000001 801d69a8 85e7bd40 801d6b34 85e7bd4c 8032dc6c 00000000 801dbc80<br> 85e7be80 864315a8 8662c980 00000001 00000742 00000000 00000000 84b85800<br> 85e7bd90 801d6cc0 7fffffff 84a42440 00000002 8032ee74 00000081 804158a0<br>
...<br>Call Trace:<br>[<8032d574>] __schedule+0x618/0x6b8 from[<8032d62c>] schedule+0x18/0x3c<br>[<8032d62c>] schedule+0x18/0x3c from[<8032dc6c>] schedule_timeout+0x2c/0x1c0<br>[<8032dc6c>] schedule_timeout+0x2c/0x1c0 from[<8032ee74>] __down+0x8c/0xdc<br>
[<8032ee74>] __down+0x8c/0xdc from[<8004500c>] down+0x40/0x88<br>[<8004500c>] down+0x40/0x88 from[<801ca838>] xfs_buf_lock+0xcc/0x15c<br>[<801ca838>] xfs_buf_lock+0xcc/0x15c from[<801b71a0>] xfs_getsb+0x38/0x54<br>
[<801b71a0>] xfs_getsb+0x38/0x54 from[<801d64a8>] xfs_sync_fsdata+0x7c/0x154<br>[<801d64a8>] xfs_sync_fsdata+0x7c/0x154 from[<801d7284>] xfs_quiesce_data+0x34/0x60<br>[<801d7284>] xfs_quiesce_data+0x34/0x60 from[<801d3514>] xfs_fs_sync_fs+0x30/0xec<br>
[<801d3514>] xfs_fs_sync_fs+0x30/0xec from[<800ba09c>] __fsync_super+0xa4/0xc8<br>[<800ba09c>] __fsync_super+0xa4/0xc8 from[<800ba0d4>] fsync_super+0x14/0x28<br>[<800ba0d4>] fsync_super+0x14/0x28 from[<800ba4a0>] generic_shutdown_super+0x34/0x190<br>
[<800ba4a0>] generic_shutdown_super+0x34/0x190 from[<800ba654>] kill_block_super+0x58/0x80<br>[<800ba654>] kill_block_super+0x58/0x80 from[<800bac6c>] deactivate_super+0x7c/0x110<br>[<800bac6c>] deactivate_super+0x7c/0x110 from[<800d2bbc>] sys_umount+0x310/0x358<br>
[<800d2bbc>] sys_umount+0x310/0x358 from[<8000ff44>] stack_done+0x20/0x3c<br>-------------------------------------------------------------------------------------<br>Filesystem "sda2": xfs_log_force: error 5 returned.</div>
<div>Please let me know in case more information is needed.<br> <br>Thanks & Regards,<br>Amit Sahrawat<br><br></div>
<div class="gmail_quote">On Wed, Dec 22, 2010 at 1:34 PM, Michael Monnerie <span dir="ltr"><<a href="mailto:michael.monnerie@is.it-management.at">michael.monnerie@is.it-management.at</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On Mittwoch, 22. Dezember 2010 Dave Chinner wrote:<br>> For future reference, when you are reporting a problem you need to<br>> be specific about what you were doing to cause the problem you are<br>
> reporting. Describe your kernel, your storage, your test case, any<br>> errors that occurred before the problem you are reporting, etc.<br>><br>> We need this information to make any sense of your bug report, but<br>
> I'm getting tired of having to ask for it every time you report a<br>> problem. The more information you put in your bug report, the more<br>> likely we are to be able to help you. We don't have unlimited<br>
> amounts of time (or patience) to drag all the basic details of your<br>> problem out of you over 3 or 4 emails, so including it up front will<br>> help a lot....<br><br></div>Should I update this section?<br><br>
<a href="http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F" target="_blank">http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F</a><br>
<br>We should probably just send that link to people so you don't have to<br>write long texts all the time.<br><br>Maybe above section should be updated to:<br><br>Things to include are what version of XFS you are using and version of<br>
the kernel. If you have problems with userland packages please report<br>the version of the package you are using.<br><br>If the problem relates to a particular filesystem, the output from the<br>xfs_info(8) command and any mount(8) options in use will also be useful<br>
to the developers.<br><br>If you experience an oops, please run it through ksymoops so that it can<br>be interpreted. Also describe what you were doing, if you can repeat it,<br>and describe you kernel, storage, test case, if there was a hardware<br>
problem before, etc.<br><br>If you have a filesystem that cannot be repaired, make sure you have<br>xfsprogs 3.1.x or later and run xfs_metadump(8) to capture the metadata<br>(which obfuscates filenames and attributes to protect your privacy) and<br>
make the dump available for someone to analyse.<br><br>--<br>mit freundlichen Grüssen,<br>Michael Monnerie, Ing. BSc<br><br>it-management Internet Services: Protéger<br><a href="http://proteger.at/" target="_blank">http://proteger.at</a> [gesprochen: Prot-e-schee]<br>
Tel: +43 660 / 415 6531<br><br>// ****** Radiointerview zum Thema Spam ******<br>// <a href="http://www.it-podcast.at/archiv.html#podcast-100716" target="_blank">http://www.it-podcast.at/archiv.html#podcast-100716</a><br>
//<br>// Haus zu verkaufen: <a href="http://zmi.at/langegg/" target="_blank">http://zmi.at/langegg/</a><br></blockquote></div><br>