On Thu, 22 Jan 2009 10:24:39 -0900, Mel
wrote:
> In short: reboot in single user mode, then run fsck -y at the prompt.
>
> Never ever run fsck -y on a live filesystem.
A very good hint. Didn't I mention it? No? Bad idea.
Background concept: The fsck utility does changes to the file system
when
On Thursday 15 January 2009 13:37:06 Polytropon wrote:
> On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote:
Added context:
> > Here's the output of fsck (this was a new command to me):
> >
> > # fsck
> > ** /dev/ar0s1a (NO WRITE)
> > Should I run fsck -y? Is it safe to do so?
>
> At least
On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote:
> Should I run fsck -y? Is it safe to do so?
At least, fsck will do its best to repair the defective file system.
As you have seen from the messages, you will surely lose some files
when their information gets cleared. If you use -y, fsck i
On Wed, Jan 14, 2009 at 7:34 PM, Andy Wodfer wrote:
> Hi,
> I'm getting an error message every week and I can't seem to understand why
> nor manage to fix it. Here it is:
>
> #dmesg
> [snip]
> pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full
>
> # df -h
> Filesystem S
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber wrote:
> On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wrote:
> > Hi,
> > I'm getting an error message every week and I can't seem to understand
> why
> > nor manage to fix it. Here it is:
> >
>
> [snip]
>
> >
> > # df -h
> > Filesystem SizeUsed
On 01/14/2009 10:34 AM, Andy Wodfer wrote:
> Hi,
> I'm getting an error message every week and I can't seem to understand why
> nor manage to fix it. Here it is:
>
> #dmesg
> [snip]
> pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full
>
> # df -h
> Filesystem SizeUs
On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wrote:
> Hi,
> I'm getting an error message every week and I can't seem to understand why
> nor manage to fix it. Here it is:
>
[snip]
>
> # df -h
> Filesystem SizeUsed Avail Capacity Mounted on
> /dev/ar0s1a989M 53M857M 6%
