Administrace komentářů

zdravím,

chybou v jádře se mi dostal filesystém (reiserfs 3.6) do nekonsistentního stavu; po rebootu na mě zařval, že se mu to nepovedlo opravit a ať spustím reiserfsck --rebuild-tree, což byl konec použitelnosti toho disku, neboť skončil řvoucí, že nemá dostatek místa

jelikož rozdělení disku vypadá následovně:

Zařízení Boot      Start         End      Blocks   Id  System
/dev/hdd1   *           1       24255   194828256   83  Linux
/dev/hdd2           24256       24321      530145   82  Linux swap / Solaris

chtěl jsem to zkusit řešit zrušením swapu a roztažením první partition na celý disk, ale parted na to nezafungoval a fdisk i sfdisk se chovají poněkud destruktivně - přesněji po jejich zásahu mi reiserfsck vždy zařve, že nemůže najít superblock, přičemž debugreiserfs, který to doporučí, je také úplně mimo a nic nenajde

pokus o reiserfsck --rebuild-sb má za následek jedině to, že mi reiserfsck --rebuild-tree po hodině a půl chrochtání řekne, že nenašel metadata ... dělal jsem zhruba následující:

# reiserfsck --rebuild-sb /dev/hdb1
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
... blabla varování ...
*************************************************************

Will check superblock and rebuild it if needed
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/hdb1.

what the version of ReiserFS do you use[1-4]
        (1)   3.6.x
        (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one)
        (3) < 3.5.9 converted to new format (don't choose if unsure)
        (4) < 3.5.9 (this is very old format, don't choose if unsure)
        (X)   exit
1

Enter block size [4096]:


No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified).
Is journal default? (y/n)[y]:

Did you use resizer(y/n)[n]: y

Enter partition size [48839600]:
rebuild-sb: no uuid found, a new uuid was generated (b09ba33c-d928-43f7-970d-ac03e02f2f74)

rebuild-sb: You either have a corrupted journal or have just changed
the start of the partition with some partition table editor. If you are
sure that the start of the partition is ok, rebuild the journal header.
Do you want to rebuild the journal header? (y/n)[n]: y
Reiserfs super block in block 16 on 0x341 of format 3.6 with standard journal
Count of blocks on the device: 48839600
Number of bitmaps: 1491
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0
Root block: 0
Filesystem is NOT clean
Tree height: 0
Hash function used to sort names: not set
Objectid map size 0, max 972
Journal parameters:
        Device [0x0]
        Magic [0x0]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x1:
         some corruptions exist.
sb_version: 2
inode generation number: 0
UUID: b09ba33c-d928-43f7-970d-ac03e02f2f74
LABEL:
Set flags in SB:
Is this ok ? (y/n)[n]: y
The fs may still be unconsistent. Run reiserfsck --check.

# reiserfsck --check /dev/hdb1
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
... blabla varování ...
*************************************************************

Will read-only check consistency of the filesystem on /dev/hdb1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Sat May 21 23:04:19 2005
###########
Replaying journal..
No transactions found
Checking internal tree..

Bad root block 0. (--rebuild-tree did not complete)

Neúspěšně ukončen (SIGABRT)
# reiserfsck --rebuild-tree -l /root/recovery.log /dev/hdb1
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
... blabla varování ...
*************************************************************

Will rebuild the filesystem (/dev/hdb1) tree
Will put log info to '/root/recovery.log'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal..
No transactions found
###########
reiserfsck --rebuild-tree started at Sat May 21 23:05:02 2005
###########

Pass 0:
Loading on-disk bitmap .. ok, 22665497 blocks marked used
Skipping 9701 blocks (super block, journal, bitmaps) 36212849 blocks will be read
0%....20%....40%....60%....80%....100%                        left 0, 8421 /sec
Selected hash ("r5") does not match to the hash set in the super block (not set).
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 36212849
                Leaves among those 0
                Objectids found 2

Pass 1 (will try to insert 0 leaves):
Looking for allocable blocks .. finished

Flushing..finished
        0 leaves read
                0 inserted
Flushing..finished


No reiserfs metadata found.  If you are sure that you had the reiserfs
on this partition,  then the start  of the partition  might be changed
or all data were wiped out. The start of the partition may get changed
by a partitioner  if you have used one.  Then you probably rebuilt the
superblock as there was no one.  Zero the block at 64K offset from the
start of the partition (a new super block you have just built) and try
to move the start of the partition a few cylinders aside  and check if
debugreiserfs /dev/xxx detects a reiserfs super block. If it does this
is likely to be the right super block version.
If this makes you nervous, try  www.namesys.com/support.html,  and for
$25 the author of fsck,  or a colleague  if he is out,  will  step you
through it all.

Neúspěšně ukončen (SIGABRT)

tak nevím, co s tím - když na tu velikost partition nešahám, tak vždycky skončí s hláškou o nedostatku místa, když se pokusím to zvětšit, tak si zas neporadí se superblockem ... a nejvíc deptající na tom je, že překopírování celého toho filesystému trvá přes 6 hodin (nechci zlikvidovat originál ještě víc, než je) a jakýkoliv experiment s --rebuild-tree další hodinu a půl

dík za každou radu (kromě toho, že mám obětovat 25 $ Namesysu )