On 30 Dec 2009, at 00:17, Albert Hopkins wrote:

... The only problem I've had
since then is one time it would not mount on boot. I merely had to
fsck
it from a live media an then it was ok (nothing SEEMED lost or
currupted).


Fixed this for you.

Stroller.

On 12/29/2009 7:17 PM, Albert Hopkins wrote:

On Wed, 2009-12-30 at 00:08 +0100, Volker Armin Hemmann wrote:


just think a moment of the tons of bug fixes constantly going into
ext4. That
crap is not stable. Pre-alpha maybe.


People say this from time to time, yet I have been running ext4 on my
root directory of my laptop since July 2008. The only problem I've had
since then is one time it would not mount on boot. I merely had to fsck
it from a live media an then it was ok (nothing lost or currupted). But
that was a long time ago when it was still ext4dev. And I've had
numerous crashes and battery depletions on the laptop without incident.
So the pre-alpha FUD that some people are spreading is either not true
or I just happen to be the luckiest ext4 user in the world :-).

For my two cents, a while back I was on ext4 and was trying to get xorg
working. My problem was that the input drivers were not working (because
they had not been recompiled after an update), so once I ran startx, no
keyboard or mouse input was registered. This meant that every time I
tried something which I thought would fix it, I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out. Even though I was running ext4, I never lost a thing (except the
logs ).


For the curious, I eventually got good logs by running shutdown -h 1 in
one tty right before running startx in the other, and that shutdown the
system correctly.


Marcus

On Mittwoch 30 Dezember 2009, Marcus Wanner wrote:
> On 12/29/2009 7:17 PM, Albert Hopkins wrote:
> > On Wed, 2009-12-30 at 00:08 +0100, Volker Armin Hemmann wrote:
> >> just think a moment of the tons of bug fixes constantly going into
> >> ext4. That
> >> crap is not stable. Pre-alpha maybe.
> >
> > People say this from time to time, yet I have been running ext4 on my
> > root directory of my laptop since July 2008. The only problem I've had
> > since then is one time it would not mount on boot. I merely had to fsck
> > it from a live media an then it was ok (nothing lost or currupted). But
> > that was a long time ago when it was still ext4dev. And I've had
> > numerous crashes and battery depletions on the laptop without incident.
> > So the pre-alpha FUD that some people are spreading is either not true
> > or I just happen to be the luckiest ext4 user in the world :-).
>
> For my two cents, a while back I was on ext4 and was trying to get xorg
> working. My problem was that the input drivers were not working (because
> they had not been recompiled after an update), so once I ran startx, no
> keyboard or mouse input was registered. This meant that every time I
> tried something which I thought would fix it, I had to hard reset the
> system and look at the logs. The only problem was that the logs had the
> wrong contents because they had been "written to" but not actually
> flushed to the disk, and it took me about 10 hard resets to figure that
> out. Even though I was running ext4, I never lost a thing (except the
> logs ).
>
> For the curious, I eventually got good logs by running shutdown -h 1 in
> one tty right before running startx in the other, and that shutdown the
> system correctly.
>
> Marcus
>

you could have set up acpid to switch to vt1 when the power button is pressed.

This is a nice safeguard against a misbehaving X.

On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:

> I had to hard reset the
> system and look at the logs. The only problem was that the logs had the
> wrong contents because they had been "written to" but not actually
> flushed to the disk, and it took me about 10 hard resets to figure that
> out.

Another reason to you the magic sysrq keys instead of the reset button.
S syncs your filesystems.


--
Neil Bothwick

Get your copy at http://www.geekthing.com/~robf/gensig/

On 12/30/2009 8:04 PM, Neil Bothwick wrote:

On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:



I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out.


Another reason to you the magic sysrq keys instead of the reset button.
S syncs your filesystems.


sysrq syncs the filesystem? I always wondered what that key actually did...

Wait, to get sysrq is Shift+printscreen, right?

Marcus

Marcus Wanner wrote:

On 12/30/2009 8:04 PM, Neil Bothwick wrote:

On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:



I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out.


Another reason to you the magic sysrq keys instead of the reset button.
S syncs your filesystems.

sysrq syncs the filesystem? I always wondered what that key actually
did...


Wait, to get sysrq is Shift+printscreen, right?

Marcus




This is from a post by Neil a good long while back:

Hold down Atl, hold down SysRq, press each of the keys in turn. The usual
full sequence is R-E-I-S-U-B

Reboot
Even
If
System
Utterly
Broken


I usually only get to the second or third key and I am back at a console.


That help?

Dale

:-) :-)

On Donnerstag 31 Dezember 2009, Dale wrote:
> Marcus Wanner wrote:
> > On 12/30/2009 8:04 PM, Neil Bothwick wrote:
> >> On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:
> >>> I had to hard reset the
> >>> system and look at the logs. The only problem was that the logs had the
> >>> wrong contents because they had been "written to" but not actually
> >>> flushed to the disk, and it took me about 10 hard resets to figure that
> >>> out.
> >>
> >> Another reason to you the magic sysrq keys instead of the reset button.
> >> S syncs your filesystems.
> >
> > sysrq syncs the filesystem? I always wondered what that key actually
> > did...
> >
> > Wait, to get sysrq is Shift+printscreen, right?
> >
> > Marcus
>
> This is from a post by Neil a good long while back:
>
> Hold down Atl, hold down SysRq, press each of the keys in turn. The usual
> full sequence is R-E-I-S-U-B
>
> Reboot
> Even
> If
> System
> Utterly
> Broken
>
>
> I usually only get to the second or third key and I am back at a console.
>

and sometimes K is all you need.

Thank god for /usr/src/linux/Documentation

Volker Armin Hemmann wrote:

On Donnerstag 31 Dezember 2009, Dale wrote:


Marcus Wanner wrote:


On 12/30/2009 8:04 PM, Neil Bothwick wrote:


On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:


I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out.


Another reason to you the magic sysrq keys instead of the reset button.
S syncs your filesystems.


sysrq syncs the filesystem? I always wondered what that key actually
did...

Wait, to get sysrq is Shift+printscreen, right?

Marcus


This is from a post by Neil a good long while back:

Hold down Atl, hold down SysRq, press each of the keys in turn. The usual
full sequence is R-E-I-S-U-B

Reboot
Even
If
System
Utterly
Broken


I usually only get to the second or third key and I am back at a console.




and sometimes K is all you need.

Thank god for /usr/src/linux/Documentation


Thanks for the info!

Marcus

Volker Armin Hemmann wrote:

On Donnerstag 31 Dezember 2009, Dale wrote:


Marcus Wanner wrote:


On 12/30/2009 8:04 PM, Neil Bothwick wrote:


On Wed, 30 Dec 2009 09:12:29 -0500, Marcus Wanner wrote:


I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out.


Another reason to you the magic sysrq keys instead of the reset button.
S syncs your filesystems.


sysrq syncs the filesystem? I always wondered what that key actually
did...

Wait, to get sysrq is Shift+printscreen, right?

Marcus


This is from a post by Neil a good long while back:

Hold down Atl, hold down SysRq, press each of the keys in turn. The usual
full sequence is R-E-I-S-U-B

Reboot
Even
If
System
Utterly
Broken


I usually only get to the second or third key and I am back at a console.




and sometimes K is all you need.

Thank god for /usr/src/linux/Documentation




This was posted by Volker a while back.


e sends TERM to all processes (except init)
i kills all processes (except init)
s syncs partitions
u remounts everything ro
b boots a box
o turns off a box
k saks a box - kills all processes on that vt

That tells what each key does. I'm still not sure which one took me back to a console. It may be the E key that does it.

Dale

:-) :-)
r unraws the keyboars - takes it away from X.

Helmut Jarausch wrote:
> Hi,
>
> I'm looking for a working and maintained compressed filesystem.
> I'd like to use it for backing up my root and my /usr filesystems,
> so that I can use rsync to keep it up-to-date.

Perhaps you could try venti+fossil or git.

cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/

cellphone: +49 174 7066481 email: info@metux.de skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------