Author: Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx>
Date: 1 Dec 2000 08:09:25 GMT
just a very trivial idea (maybe wrong): i think i have seen this then i did not change the lilo entry for the xfs root from read-only to read-write ... but i might be wrong ... but if that should be
There are manual pages for kdb, "man Documentation/kdb/kdb.mm" for an overview, then read the other man pages. Little known Linux fact, if the 'man' command is given a name that contains '/' then it
[ ... ] [ ... ] First, the immediate BUG() is due to a bogus sized kmalloc being requested. Second, I've been seeing problems here with recovery; so far I thought it was a bug in code that I've been
i repeated the test: - booting with the good kernel to recover the filesytem. - cp -av /usr/src/linux/ /tmp/ - hardreset - booting the bad kernel [...] fatfs: bogus cluster size fatfs: bogus cluster
it works! i made 2 tests with it: it works. then i made 3 tests with following procedure: - cp -av - boot the bad kernel. it hangs or crashend. - boot with the patched kernel. recovery works. thanks!
Cool ... I'll try similar experiments here as well. Good to see that recovery works inspite of a fairly serious bug! regards, -- Rajagopal Ananthanarayanan ("ananth") Member Technical Staff, SGI. --
I've actually recently hit the same bug. But it looks like Ananth hit the nail on the head and found the problem. Keep the cable handy :-) -- Russell Cattelan cattelan@xxxxxxxxxxx
Author: Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx>
Date: 1 Dec 2000 08:09:25 GMT
just a very trivial idea (maybe wrong): i think i have seen this then i did not change the lilo entry for the xfs root from read-only to read-write ... but i might be wrong ... but if that should be
There are manual pages for kdb, "man Documentation/kdb/kdb.mm" for an overview, then read the other man pages. Little known Linux fact, if the 'man' command is given a name that contains '/' then it
[ ... ] [ ... ] First, the immediate BUG() is due to a bogus sized kmalloc being requested. Second, I've been seeing problems here with recovery; so far I thought it was a bug in code that I've been
i repeated the test: - booting with the good kernel to recover the filesytem. - cp -av /usr/src/linux/ /tmp/ - hardreset - booting the bad kernel [...] fatfs: bogus cluster size fatfs: bogus cluster
it works! i made 2 tests with it: it works. then i made 3 tests with following procedure: - cp -av - boot the bad kernel. it hangs or crashend. - boot with the patched kernel. recovery works. thanks!
Cool ... I'll try similar experiments here as well. Good to see that recovery works inspite of a fairly serious bug! regards, -- Rajagopal Ananthanarayanan ("ananth") Member Technical Staff, SGI. --
I've actually recently hit the same bug. But it looks like Ananth hit the nail on the head and found the problem. Keep the cable handy :-) -- Russell Cattelan cattelan@xxxxxxxxxxx