<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: bad fsck!</title>
	<atom:link href="http://malvasiabianca.org/archives/2007/06/bad-fsck/feed/" rel="self" type="application/rss+xml" />
	<link>http://malvasiabianca.org/archives/2007/06/bad-fsck/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 06:10:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: malvasia bianca &#187; Blog Archive &#187; good fsck!</title>
		<link>http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46997</link>
		<dc:creator>malvasia bianca &#187; Blog Archive &#187; good fsck!</dc:creator>
		<pubDate>Sun, 10 Jun 2007 23:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46997</guid>
		<description>[...] I reported my problem to the author of fsck yesterday; today, I had an e-mail waiting for me, saying he thought it was a bug he&#8217;d fixed recently, and asking me to try a new version. I did, and at first it seemed to get stuck in the same place; while I was poking around and composing a response, though, I noticed that it had made it further, and the scan did eventually complete. (Reporting no problems.) So either the new version fixed the problem, or I wasn&#8217;t patient enough the first time. [...]</description>
		<content:encoded><![CDATA[<p>[...] I reported my problem to the author of fsck yesterday; today, I had an e-mail waiting for me, saying he thought it was a bug he&#8217;d fixed recently, and asking me to try a new version. I did, and at first it seemed to get stuck in the same place; while I was poking around and composing a response, though, I noticed that it had made it further, and the scan did eventually complete. (Reporting no problems.) So either the new version fixed the problem, or I wasn&#8217;t patient enough the first time. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david carlton</title>
		<link>http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46989</link>
		<dc:creator>david carlton</dc:creator>
		<pubDate>Sun, 10 Jun 2007 22:43:17 +0000</pubDate>
		<guid isPermaLink="false">http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46989</guid>
		<description>I'm using ext3 on top of lvm.  Thanks for the kernel command line tip!</description>
		<content:encoded><![CDATA[<p>I&#8217;m using ext3 on top of lvm.  Thanks for the kernel command line tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Praveen</title>
		<link>http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46969</link>
		<dc:creator>Praveen</dc:creator>
		<pubDate>Sun, 10 Jun 2007 18:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://malvasiabianca.org/archives/2007/06/bad-fsck/#comment-46969</guid>
		<description>I am wondering about your filesystem type! I am assuming that you run a journaling one (probably ext3 or resiserfs?). I am using reiserfs. I have never come across this issue and my filesystem is rolling for around 2 years now.

QUOTE BEGINS
Make sure your computer has a root password, and you know it! (Not always the case in this sudo world.)
QUOTE ENDS

Even if you don't have the root password, you can fix things by dropping directly into bash(using 'init=/bin/bash' to the kernel command line). Alternatively, one can use a live/rescue CD.</description>
		<content:encoded><![CDATA[<p>I am wondering about your filesystem type! I am assuming that you run a journaling one (probably ext3 or resiserfs?). I am using reiserfs. I have never come across this issue and my filesystem is rolling for around 2 years now.</p>
<p>QUOTE BEGINS<br />
Make sure your computer has a root password, and you know it! (Not always the case in this sudo world.)<br />
QUOTE ENDS</p>
<p>Even if you don&#8217;t have the root password, you can fix things by dropping directly into bash(using &#8216;init=/bin/bash&#8217; to the kernel command line). Alternatively, one can use a live/rescue CD.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
