<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>could be. i gather the e2fsck data structures are huge.</div><div><br></div>I wonder if using a scratch file would be any faster than having the system do the paging.<div><br></div><div>frustratingly, fewer than 5% of the inodes have been identified by fsck as suspect and I would be happy to delete them just to get the remaining files back online.</div><div><br></div><div><br></div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-size: 12px; "><div>Professor Samuel Aparicio BM BCh PhD FRCPath</div><div>Nan and Lorraine Robertson Chair UBC/BC Cancer Agency</div><div>675 West 10th, Vancouver V5Z 1L3, Canada.</div><div>office: +1 604 675 8200 lab website <a href="http://molonc.bccrc.ca/">http://molonc.bccrc.ca</a></div></span><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jul 5, 2012, at 11:01 AM, Mark Hahn wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">yes, I do - e2fsck identifies the suspect inodes, so they could be deleted with debugfs<br></blockquote><br>close to a WAG, but I doubt this would help. I think the scaling <br>issue you're running into is a function of the inodes you want to keep...<br><br>simply speeding up the swapping is an unspeakable hack, but could <br>actually be done cheaply and possibly even without interrupting the <br>current fsck ;)<br></div></blockquote></div><br></div></body></html>