Joachim Schipper wrote:
>>> make a dump of the partition before going to execute potentially data
>>> destroying actions?
>> yes, this is sound advice of course. but what are you going
>> to do with the dump if say, fsck is not able to revive the fs?
>> "dump" it back, run fsck again and answer "n
On Sun, Oct 4, 2009 at 3:10 AM, Anthony Roberts
wrote:
> What I tend to do for those is just make the filesystems for that machine
> read-only.
>
> This is inconvenient to set up/use for several reasons, but it helps make
> machines indifferent to surprise reboots. It's handy if the site has
> unr
On Sun, Oct 4, 2009 at 11:26 AM, bofh wrote:
> What does fsck mean?
>
Filesystem check.
On Sun, Oct 04, 2009 at 07:58:06PM +0200, frantisek holop wrote:
> hmm, on Fri, Oct 02, 2009 at 10:49:56PM +0200, Otto Moerbeek said that
> > > here's the thing: even though every single diagnostic message
> > > fsck may produce is documented in /usr/share/doc/smm/03.fsck_ffs
> > > i dont see how t
What does fsck mean? I always thought it was those strange bearded
sysadmins private cuss word as they always seem to scream *fsck yes
damnit!!!* whenever the system crashes
On 10/2/09, frantisek holop wrote:
> hmm, on Fri, Oct 02, 2009 at 07:31:39PM +0200, Otto Moerbeek said that
>> > fsck
On Sun, Oct 04, 2009 at 07:58:06PM +0200, frantisek holop wrote:
> hmm, on Fri, Oct 02, 2009 at 10:49:56PM +0200, Otto Moerbeek said that
> > > here's the thing: even though every single diagnostic message
> > > fsck may produce is documented in /usr/share/doc/smm/03.fsck_ffs
> > > i dont see how
hmm, on Fri, Oct 02, 2009 at 10:49:56PM +0200, Otto Moerbeek said that
> > here's the thing: even though every single diagnostic message
> > fsck may produce is documented in /usr/share/doc/smm/03.fsck_ffs
> > i dont see how these questions help at all. what i mean is,
> > there is nothing to comp
What I tend to do for those is just make the filesystems for that machine
read-only.
This is inconvenient to set up/use for several reasons, but it helps make
machines indifferent to surprise reboots. It's handy if the site has
unreliable power (eg solar/battery out in the bush somewhere) or even
Hi,
> If that was a wisething to do, we would have already done so. In other
> words, it is not wise. It's foolish.
>
> -Otto
I totally agree with you. This should not be in the release.
However, I have a few obsd boxes working at places where I can
not reach with ease. What I want to avoi
Otto Moerbeek wrote:
Note that I said "dump the partition", not "dump the filesystem".
Oops. you mean dd(1)... sorry for the noise
--
Mauro Rezzonico , Como, Italia
"Maybe this world is another planet's hell" - H.Huxley
On Sat, Oct 03, 2009 at 12:12:39AM +0200, Mauro Rezzonico wrote:
> Otto Moerbeek wrote:
> >make a dump of the partition before going to execute potentially data
> >destroying actions?
>
> So you can dump a botched filesystem? The manpage says nothing about that...
> Well it doesn't say the contra
On Sat, 03 Oct 2009 00:12:39 +0200
Mauro Rezzonico wrote:
> Otto Moerbeek wrote:
> > make a dump of the partition before going to execute potentially
> > data destroying actions?
>
> So you can dump a botched filesystem? The manpage says nothing about
> that... Well it doesn't say the contrary b
Otto Moerbeek wrote:
make a dump of the partition before going to execute potentially data
destroying actions?
So you can dump a botched filesystem? The manpage says nothing about that...
Well it doesn't say the contrary but...
So, question is: Can you *really* dump a "borked fs"?
--
Mauro Re
On Fri, Oct 02, 2009 at 10:38:16PM +0200, frantisek holop wrote:
> hmm, on Fri, Oct 02, 2009 at 07:31:39PM +0200, Otto Moerbeek said that
> > > fsck -y
> > >
> > > after a power or other type of failure,
> > > in cases the automatic file system check fails?
> >
> > If that was a wisething to do,
On Fri, Oct 2, 2009 at 4:38 PM, frantisek holop wrote:
> if fsck thinks there is a problem, there is nothing left but to press y
> anyway. B although i'd very much like to read stories of other admins
> doing otherwise.
Put a rock on the 'y' key and go get some coffee.
hmm, on Fri, Oct 02, 2009 at 07:31:39PM +0200, Otto Moerbeek said that
> > fsck -y
> >
> > after a power or other type of failure,
> > in cases the automatic file system check fails?
>
> If that was a wisething to do, we would have already done so. In other
> words, it is not wise. It's foolish.
On Fri, Oct 02, 2009 at 09:15:41AM -0300, Jose Fragoso wrote:
> Hi,
>
> Is it possible to automate the process of
> running
>
> fsck -y
>
> after a power or other type of failure,
> in cases the automatic file system check fails?
If that was a wisething to do, we would have already done so. In
Jose, this is an ugly modification in /etc/rc but it should do what you
need.
Search for the line that starts with 8) and modify it to look like this:
8)
echo "Corro FSCK de emergencia..."
fsck -y ; fsck_st=$?
if [ $fsck_st != 0 ]; then
Hi,
Is it possible to automate the process of
running
fsck -y
after a power or other type of failure,
in cases the automatic file system check fails?
Thanks in advance.
Regards,
Jose
--
An Excellent Credit Score is 750
See Yours in Just 2 Easy Steps!
19 matches
Mail list logo
