* command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc
@ 2012-01-29 4:15 doiggl
2012-01-29 7:51 ` Jonáš Vidra
0 siblings, 1 reply; 14+ messages in thread
From: doiggl @ 2012-01-29 4:15 UTC (permalink / raw)
To: reiserfs-devel
Hello,
I did a repair on a reiser4 partition as follows:
# fsck.reiser4 --build-fs /dev/sdc
The disk report is listed at [1]
Is the report ok ?
See[1]
I then tried to use the disk and the command mount failed /dev/sdc
/media/disk2
See[2]
Questions:
Do I rerun the command again ? fsck.reiser4 --build-fs /dev/sdc
What else do I need to do to use the disk ?
I checked for reiser4.ko too
# ll /lib/modules/`uname -r`/kernel/fs/reiser4
total 645
-rw-r--r-- 1 root root 658032 Jan 28 19:54 reiser4.ko
Thanks Glenn
[1]
# fsck.reiser4 --build-fs /dev/sdc
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Sun Jan 29 02:37:21 2012
Reiser4 fs was detected on /dev/sdc.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 197008413
Nodes left in the tree 197008413
Leaves of them 194764277, Twigs of them 2217790
Time interval: Sun Jan 29 02:39:18 2012 - Sun Jan 29 11:20:38 2012
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Sun Jan 29 11:20:38 2012 - Sun Jan 29 13:30:57 2012
LOOKING FOR UNCONNECTED NODES
FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) and
(1): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79)
and (80): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24)
and (25): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73)
and (74): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (116595727), items (20)
and (21): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22)
and (23): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61)
and (62): Wrong order of keys.
Read nodes 1481038
Good nodes 471512
Leaves of them 466164, Twigs of them 5348
Time interval: Sun Jan 29 13:31:14 2012 - Sun Jan 29 13:35:04 2012
***** fsck.reiser4 finished at Sun Jan 29 13:35:04 2012
Closing fs...done
FS is consistent.
[2]
# mount /dev/sdc /media/disk2
mount: No such file or directory
This did not work either
mount -t reiser4 /dev/sdc /media/disk2
mount: No such file or directory
Other details
-------------
# cd /media
# md disk2
# ll
total 3
drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk
drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2
# fdisk -l
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders, total 125045424 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xcc791374
Device Boot Start End Blocks Id System
/dev/sda1 63 41046074 20523006 7 HPFS/NTFS/exFAT
/dev/sda2 * 41048064 61528063 10240000 83 Linux
/dev/sda3 61528950 120937319 29704185 83 Linux
/dev/sda4 120937320 125033894 2048287+ 82 Linux swap /
Solaris
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe0c5913d
Device Boot Start End Blocks Id System
/dev/sdb1 63 40965749 20482843+ 1c Hidden W95 FAT32
(LBA)
/dev/sdb2 * 40965750 84430847 21732549 7 HPFS/NTFS/exFAT
/dev/sdb3 285153280 976771071 345808896 f W95 Ext'd (LBA)
/dev/sdb4 84430848 285153279 100361216 83 Linux
/dev/sdb5 285155328 305903615 10374144 7 HPFS/NTFS/exFAT
/dev/sdb6 305905664 976771071 335432704 83 Linux
Partition table entries are not in disk order
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/sdc doesn't contain a valid partition table
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-29 4:15 command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc doiggl @ 2012-01-29 7:51 ` Jonáš Vidra 2012-01-29 13:35 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: Jonáš Vidra @ 2012-01-29 7:51 UTC (permalink / raw) To: reiserfs-devel, doiggl Dne Sun, 29 Jan 2012 05:15:48 +0100 <doiggl@velocitynet.com.au> napsal(a): > Hello, > I did a repair on a reiser4 partition as follows: > # fsck.reiser4 --build-fs /dev/sdc > > … > > # mount /dev/sdc /media/disk2 > mount: No such file or directory > > This did not work either > mount -t reiser4 /dev/sdc /media/disk2 > mount: No such file or directory > > Other details > ------------- > # cd /media > # md disk2 > # ll > total 3 > drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk > drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 Hello, I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did the directory /media/disk2 exist at the time you were trying to mount to it? Does your syslog contain anything useful? -- Jonáš Vidra, vidra.jonas@seznam.cz -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-29 7:51 ` Jonáš Vidra @ 2012-01-29 13:35 ` doiggl 2012-01-29 15:24 ` Edward Shishkin 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-01-29 13:35 UTC (permalink / raw) To: reiserfs-devel On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš Vidra <vidra.jonas@seznam.cz> wrote: > Dne Sun, 29 Jan 2012 05:15:48 +0100 <doiggl@velocitynet.com.au> napsal(a): > >> Hello, >> I did a repair on a reiser4 partition as follows: >> # fsck.reiser4 --build-fs /dev/sdc >> >> … >> >> # mount /dev/sdc /media/disk2 >> mount: No such file or directory >> >> This did not work either >> mount -t reiser4 /dev/sdc /media/disk2 >> mount: No such file or directory >> >> Other details >> ------------- >> # cd /media >> # md disk2 >> # ll >> total 3 >> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 > > Hello, > > I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did the > directory /media/disk2 exist at the time you were trying to mount to it? > Does your syslog contain anything useful? Hello Did the directory /media/disk2 exist at the time you were trying to mount to it? Yes Does your syslog contain anything useful? # dmesg contans the following warnings: [41535.199439] Loading Reiser4. See www.namesys.com for a description of Reiser4. [41535.205895] reiser4: sdc: found disk format 4.0.0. [41644.512374] reiser4[mount(3109)]: traverse_tree (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: [41644.512380] WARNING: not found on internal node: level: 6, lock_level: 1, stop_level: 1 lock_mode: read, bias: exact [41644.512395] reiser4[mount(3109)]: key_warning (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: [41644.512400] WARNING: Error for inode 42 (-2) [44813.457093] reiser4: sdc: found disk format 4.0.0. [44923.248153] reiser4[mount(13238)]: traverse_tree (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: [44923.248158] WARNING: not found on internal node: level: 6, lock_level: 1, stop_level: 1 lock_mode: read, bias: exact [44923.248173] reiser4[mount(13238)]: key_warning (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: [44923.248178] WARNING: Error for inode 42 (-2) Question: How are the warnings fixed ? Thanks Glenn -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-29 13:35 ` doiggl @ 2012-01-29 15:24 ` Edward Shishkin 2012-01-31 1:06 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: Edward Shishkin @ 2012-01-29 15:24 UTC (permalink / raw) To: doiggl; +Cc: reiserfs-devel On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: > On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš Vidra<vidra.jonas@seznam.cz> > wrote: >> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> > napsal(a): >> >>> Hello, >>> I did a repair on a reiser4 partition as follows: >>> # fsck.reiser4 --build-fs /dev/sdc >>> >>> … >>> >>> # mount /dev/sdc /media/disk2 >>> mount: No such file or directory >>> >>> This did not work either >>> mount -t reiser4 /dev/sdc /media/disk2 >>> mount: No such file or directory >>> >>> Other details >>> ------------- >>> # cd /media >>> # md disk2 >>> # ll >>> total 3 >>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >> >> Hello, >> >> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did the >> directory /media/disk2 exist at the time you were trying to mount to it? >> Does your syslog contain anything useful? > Hello > Did the directory /media/disk2 exist at the time you were trying to mount > to it? Yes > > Does your syslog contain anything useful? > # dmesg contans the following warnings: > [41535.199439] Loading Reiser4. See www.namesys.com for a description of > Reiser4. > [41535.205895] reiser4: sdc: found disk format 4.0.0. > [41644.512374] reiser4[mount(3109)]: traverse_tree > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: > [41644.512380] WARNING: not found on internal node: level: 6, lock_level: > 1, stop_level: 1 lock_mode: read, bias: exact > [41644.512395] reiser4[mount(3109)]: key_warning > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: > [41644.512400] WARNING: Error for inode 42 (-2) > [44813.457093] reiser4: sdc: found disk format 4.0.0. > [44923.248153] reiser4[mount(13238)]: traverse_tree > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: > [44923.248158] WARNING: not found on internal node: level: 6, lock_level: > 1, stop_level: 1 lock_mode: read, bias: exact > [44923.248173] reiser4[mount(13238)]: key_warning > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: > [44923.248178] WARNING: Error for inode 42 (-2) > Looks like stat-data of root inode can not be found at mount time. Could you please run fsck.reiser4 --check /dev/sdc and send the output? Thanks, Edward. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-29 15:24 ` Edward Shishkin @ 2012-01-31 1:06 ` doiggl 2012-01-31 7:50 ` Edward Shishkin 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-01-31 1:06 UTC (permalink / raw) To: reiserfs-devel On Sun, 29 Jan 2012 16:24:11 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: >> On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš Vidra<vidra.jonas@seznam.cz> >> wrote: >>> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> >> napsal(a): >>> >>>> Hello, >>>> I did a repair on a reiser4 partition as follows: >>>> # fsck.reiser4 --build-fs /dev/sdc >>>> >>>> … >>>> >>>> # mount /dev/sdc /media/disk2 >>>> mount: No such file or directory >>>> >>>> This did not work either >>>> mount -t reiser4 /dev/sdc /media/disk2 >>>> mount: No such file or directory >>>> >>>> Other details >>>> ------------- >>>> # cd /media >>>> # md disk2 >>>> # ll >>>> total 3 >>>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >>> >>> Hello, >>> >>> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did the >>> directory /media/disk2 exist at the time you were trying to mount to it? >>> Does your syslog contain anything useful? >> Hello >> Did the directory /media/disk2 exist at the time you were trying to mount >> to it? Yes >> >> Does your syslog contain anything useful? >> # dmesg contans the following warnings: >> [41535.199439] Loading Reiser4. See www.namesys.com for a description of >> Reiser4. >> [41535.205895] reiser4: sdc: found disk format 4.0.0. >> [41644.512374] reiser4[mount(3109)]: traverse_tree >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >> [41644.512380] WARNING: not found on internal node: level: 6, lock_level: >> 1, stop_level: 1 lock_mode: read, bias: exact >> [41644.512395] reiser4[mount(3109)]: key_warning >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >> [41644.512400] WARNING: Error for inode 42 (-2) >> [44813.457093] reiser4: sdc: found disk format 4.0.0. >> [44923.248153] reiser4[mount(13238)]: traverse_tree >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >> [44923.248158] WARNING: not found on internal node: level: 6, lock_level: >> 1, stop_level: 1 lock_mode: read, bias: exact >> [44923.248173] reiser4[mount(13238)]: key_warning >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >> [44923.248178] WARNING: Error for inode 42 (-2) >> > > Looks like stat-data of root inode can not be found at mount time. > Could you please run fsck.reiser4 --check /dev/sdc and send the output? > > Thanks, > Edward. Hello, I run the command [it took some time] and the result was as follows: # fsck.reiser4 --check /dev/sdc ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdc block device. Will check the consistency of the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): yes ***** fsck.reiser4 started at Mon Jan 30 23:10:17 2012 Reiser4 fs was detected on /dev/sdc. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede label: <none> Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x1ddaf754 flushes: 0 blocks: 488378640 free blocks: 217146980 root block: 37017218 tail policy: 0x2 (smart) next oid: 0xedade file count: 188313 tree height: 6 key policy: LARGE CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree 197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval: Mon Jan 30 23:12:14 2012 - Tue Jan 31 07:48:37 2012 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Tue Jan 31 07:48:37 2012 - Tue Jan 31 09:58:54 2012 CHECKING THE SEMANTIC TREE FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the plugin for the directory [29:0:2a]. FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory opened. Time interval: Tue Jan 31 09:58:54 2012 - Tue Jan 31 09:58:54 2012 FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really used block bitmap differ. ***** fsck.reiser4 finished at Tue Jan 31 09:58:54 2012 Closing fs...done 2 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-31 1:06 ` doiggl @ 2012-01-31 7:50 ` Edward Shishkin 2012-01-31 12:44 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: Edward Shishkin @ 2012-01-31 7:50 UTC (permalink / raw) To: doiggl; +Cc: reiserfs-devel On 01/31/2012 02:06 AM, doiggl@velocitynet.com.au wrote: > On Sun, 29 Jan 2012 16:24:11 +0100, Edward Shishkin > <edward.shishkin@gmail.com> wrote: >> On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: >>> On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš > Vidra<vidra.jonas@seznam.cz> >>> wrote: >>>> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> >>> napsal(a): >>>> >>>>> Hello, >>>>> I did a repair on a reiser4 partition as follows: >>>>> # fsck.reiser4 --build-fs /dev/sdc >>>>> >>>>> … >>>>> >>>>> # mount /dev/sdc /media/disk2 >>>>> mount: No such file or directory >>>>> >>>>> This did not work either >>>>> mount -t reiser4 /dev/sdc /media/disk2 >>>>> mount: No such file or directory >>>>> >>>>> Other details >>>>> ------------- >>>>> # cd /media >>>>> # md disk2 >>>>> # ll >>>>> total 3 >>>>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>>>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >>>> >>>> Hello, >>>> >>>> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did > the >>>> directory /media/disk2 exist at the time you were trying to mount to > it? >>>> Does your syslog contain anything useful? >>> Hello >>> Did the directory /media/disk2 exist at the time you were trying to > mount >>> to it? Yes >>> >>> Does your syslog contain anything useful? >>> # dmesg contans the following warnings: >>> [41535.199439] Loading Reiser4. See www.namesys.com for a description > of >>> Reiser4. >>> [41535.205895] reiser4: sdc: found disk format 4.0.0. >>> [41644.512374] reiser4[mount(3109)]: traverse_tree >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>> [41644.512380] WARNING: not found on internal node: level: 6, > lock_level: >>> 1, stop_level: 1 lock_mode: read, bias: exact >>> [41644.512395] reiser4[mount(3109)]: key_warning >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>> [41644.512400] WARNING: Error for inode 42 (-2) >>> [44813.457093] reiser4: sdc: found disk format 4.0.0. >>> [44923.248153] reiser4[mount(13238)]: traverse_tree >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>> [44923.248158] WARNING: not found on internal node: level: 6, > lock_level: >>> 1, stop_level: 1 lock_mode: read, bias: exact >>> [44923.248173] reiser4[mount(13238)]: key_warning >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>> [44923.248178] WARNING: Error for inode 42 (-2) >>> >> >> Looks like stat-data of root inode can not be found at mount time. >> Could you please run fsck.reiser4 --check /dev/sdc and send the output? >> >> Thanks, >> Edward. > Hello, > I run the command [it took some time] and the result was as follows: > # fsck.reiser4 --check /dev/sdc > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/sdc block device. > > Will check the consistency of the Reiser4 SuperBlock. > > Will check the consistency of the Reiser4 FileSystem. > > Continue? > > (Yes/No): yes > ***** fsck.reiser4 started at Mon Jan 30 23:10:17 2012 > Reiser4 fs was detected on /dev/sdc. > > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede > label:<none> > > Format super block (17): > plugin: format40 > description: Disk-format plugin. > version: 0 > magic: ReIsEr40FoRmAt > mkfs id: 0x1ddaf754 > flushes: 0 > blocks: 488378640 > free blocks: 217146980 > root block: 37017218 > tail policy: 0x2 (smart) > next oid: 0xedade > file count: 188313 > tree height: 6 > key policy: LARGE > > > CHECKING THE STORAGE TREE > > Read nodes 197008413 > > Nodes left in the tree 197008413 > Leaves of them 194764277, Twigs of them 2217790 > Time interval: Mon Jan 30 23:12:14 2012 - Tue Jan 31 07:48:37 2012 > > CHECKING EXTENT REGIONS. > > Read twigs 2217790 > > Time interval: Tue Jan 31 07:48:37 2012 - Tue Jan 31 09:58:54 2012 > > CHECKING THE SEMANTIC TREE > > FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the > plugin for the directory [29:0:2a]. > FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory > opened. > Time interval: Tue Jan 31 09:58:54 2012 - Tue Jan 31 09:58:54 2012 > > FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really > used block bitmap differ. > ***** fsck.reiser4 finished at Tue Jan 31 09:58:54 2012 > Closing fs...done > > 2 fatal corruptions were detected in FileSystem. Run with --build-fs > option to fix them. Ok, thanks, now please, run "fsck.reiser4 --build-fs /dev/sdc", and after its completion run "fsck.reiser4 --check /dev/sdc" again, then send the both outputs. Edward. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-01-31 7:50 ` Edward Shishkin @ 2012-01-31 12:44 ` doiggl [not found] ` <4F27F2BA.8090300@gmail.com> 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-01-31 12:44 UTC (permalink / raw) To: reiserfs-devel On Tue, 31 Jan 2012 08:50:26 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 01/31/2012 02:06 AM, doiggl@velocitynet.com.au wrote: >> On Sun, 29 Jan 2012 16:24:11 +0100, Edward Shishkin >> <edward.shishkin@gmail.com> wrote: >>> On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: >>>> On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš >> Vidra<vidra.jonas@seznam.cz> >>>> wrote: >>>>> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> >>>> napsal(a): >>>>> >>>>>> Hello, >>>>>> I did a repair on a reiser4 partition as follows: >>>>>> # fsck.reiser4 --build-fs /dev/sdc >>>>>> >>>>>> … >>>>>> >>>>>> # mount /dev/sdc /media/disk2 >>>>>> mount: No such file or directory >>>>>> >>>>>> This did not work either >>>>>> mount -t reiser4 /dev/sdc /media/disk2 >>>>>> mount: No such file or directory >>>>>> >>>>>> Other details >>>>>> ------------- >>>>>> # cd /media >>>>>> # md disk2 >>>>>> # ll >>>>>> total 3 >>>>>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>>>>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >>>>> >>>>> Hello, >>>>> >>>>> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did >> the >>>>> directory /media/disk2 exist at the time you were trying to mount to >> it? >>>>> Does your syslog contain anything useful? >>>> Hello >>>> Did the directory /media/disk2 exist at the time you were trying to >> mount >>>> to it? Yes >>>> >>>> Does your syslog contain anything useful? >>>> # dmesg contans the following warnings: >>>> [41535.199439] Loading Reiser4. See www.namesys.com for a description >> of >>>> Reiser4. >>>> [41535.205895] reiser4: sdc: found disk format 4.0.0. >>>> [41644.512374] reiser4[mount(3109)]: traverse_tree >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>> [41644.512380] WARNING: not found on internal node: level: 6, >> lock_level: >>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>> [41644.512395] reiser4[mount(3109)]: key_warning >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>> [41644.512400] WARNING: Error for inode 42 (-2) >>>> [44813.457093] reiser4: sdc: found disk format 4.0.0. >>>> [44923.248153] reiser4[mount(13238)]: traverse_tree >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>> [44923.248158] WARNING: not found on internal node: level: 6, >> lock_level: >>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>> [44923.248173] reiser4[mount(13238)]: key_warning >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>> [44923.248178] WARNING: Error for inode 42 (-2) >>>> >>> >>> Looks like stat-data of root inode can not be found at mount time. >>> Could you please run fsck.reiser4 --check /dev/sdc and send the output? >>> >>> Thanks, >>> Edward. >> Hello, >> I run the command [it took some time] and the result was as follows: >> # fsck.reiser4 --check /dev/sdc >> ******************************************************************* >> This is an EXPERIMENTAL version of fsck.reiser4. Read README first. >> ******************************************************************* >> >> Fscking the /dev/sdc block device. >> >> Will check the consistency of the Reiser4 SuperBlock. >> >> Will check the consistency of the Reiser4 FileSystem. >> >> Continue? >> >> (Yes/No): yes >> ***** fsck.reiser4 started at Mon Jan 30 23:10:17 2012 >> Reiser4 fs was detected on /dev/sdc. >> >> Master super block (16): >> magic: ReIsEr4 >> blksize: 4096 >> format: 0x0 (format40) >> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede >> label:<none> >> >> Format super block (17): >> plugin: format40 >> description: Disk-format plugin. >> version: 0 >> magic: ReIsEr40FoRmAt >> mkfs id: 0x1ddaf754 >> flushes: 0 >> blocks: 488378640 >> free blocks: 217146980 >> root block: 37017218 >> tail policy: 0x2 (smart) >> next oid: 0xedade >> file count: 188313 >> tree height: 6 >> key policy: LARGE >> >> >> CHECKING THE STORAGE TREE >> >> Read nodes 197008413 >> >> Nodes left in the tree 197008413 >> Leaves of them 194764277, Twigs of them 2217790 >> Time interval: Mon Jan 30 23:12:14 2012 - Tue Jan 31 07:48:37 >> 2012 >> >> CHECKING EXTENT REGIONS. >> >> Read twigs 2217790 >> >> Time interval: Tue Jan 31 07:48:37 2012 - Tue Jan 31 09:58:54 >> 2012 >> >> CHECKING THE SEMANTIC TREE >> >> FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the >> plugin for the directory [29:0:2a]. >> FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory >> opened. >> Time interval: Tue Jan 31 09:58:54 2012 - Tue Jan 31 09:58:54 >> 2012 >> >> FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and >> really >> used block bitmap differ. >> ***** fsck.reiser4 finished at Tue Jan 31 09:58:54 2012 >> Closing fs...done >> >> 2 fatal corruptions were detected in FileSystem. Run with --build-fs >> option to fix them. > > > Ok, thanks, > > now please, run "fsck.reiser4 --build-fs /dev/sdc", > and after its completion run "fsck.reiser4 --check /dev/sdc" again, > then send the both outputs. > > Edward. > > -- > To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Hello, Content of # fsck.reiser4 --build-fs /dev/sdc ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdc block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): yes ***** fsck.reiser4 started at Tue Jan 31 12:48:54 2012 Reiser4 fs was detected on /dev/sdc. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede label: <none> Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x1ddaf754 flushes: 0 blocks: 488378640 free blocks: 217146980 root block: 37017218 tail policy: 0x2 (smart) next oid: 0xedade file count: 188313 tree height: 6 key policy: LARGE CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree 197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval: Tue Jan 31 12:50:54 2012 - Tue Jan 31 21:23:12 2012 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Tue Jan 31 21:23:12 2012 - Tue Jan 31 23:33:35 2012 LOOKING FOR UNCONNECTED NODES FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) and (1): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79) and (80): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24) and (25): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73) and (74): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (116595727), items (20) and (21): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) and (23): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) and (62): Wrong order of keys. Read nodes 1481038 Good nodes 471512 Leaves of them 466164, Twigs of them 5348 Time interval: Tue Jan 31 23:33:53 2012 - Tue Jan 31 23:37:46 2012 ***** fsck.reiser4 finished at Tue Jan 31 23:37:46 2012 Closing fs...done FS is consistent. - Next step fsck.reiser4 --check /dev/sdc -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
[parent not found: <4F27F2BA.8090300@gmail.com>]
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc [not found] ` <4F27F2BA.8090300@gmail.com> @ 2012-02-01 1:16 ` doiggl 2012-02-01 16:20 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-02-01 1:16 UTC (permalink / raw) To: reiserfs-devel On Tue, 31 Jan 2012 14:55:06 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 01/31/2012 01:44 PM, doiggl@velocitynet.com.au wrote: >> On Tue, 31 Jan 2012 08:50:26 +0100, Edward Shishkin >> <edward.shishkin@gmail.com> wrote: >>> On 01/31/2012 02:06 AM, doiggl@velocitynet.com.au wrote: >>>> On Sun, 29 Jan 2012 16:24:11 +0100, Edward Shishkin >>>> <edward.shishkin@gmail.com> wrote: >>>>> On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: >>>>>> On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš >>>> Vidra<vidra.jonas@seznam.cz> >>>>>> wrote: >>>>>>> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> >>>>>> napsal(a): >>>>>>> >>>>>>>> Hello, >>>>>>>> I did a repair on a reiser4 partition as follows: >>>>>>>> # fsck.reiser4 --build-fs /dev/sdc >>>>>>>> >>>>>>>> … >>>>>>>> >>>>>>>> # mount /dev/sdc /media/disk2 >>>>>>>> mount: No such file or directory >>>>>>>> >>>>>>>> This did not work either >>>>>>>> mount -t reiser4 /dev/sdc /media/disk2 >>>>>>>> mount: No such file or directory >>>>>>>> >>>>>>>> Other details >>>>>>>> ------------- >>>>>>>> # cd /media >>>>>>>> # md disk2 >>>>>>>> # ll >>>>>>>> total 3 >>>>>>>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>>>>>>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? Did >>>> the >>>>>>> directory /media/disk2 exist at the time you were trying to mount to >>>> it? >>>>>>> Does your syslog contain anything useful? >>>>>> Hello >>>>>> Did the directory /media/disk2 exist at the time you were trying to >>>> mount >>>>>> to it? Yes >>>>>> >>>>>> Does your syslog contain anything useful? >>>>>> # dmesg contans the following warnings: >>>>>> [41535.199439] Loading Reiser4. See www.namesys.com for a description >>>> of >>>>>> Reiser4. >>>>>> [41535.205895] reiser4: sdc: found disk format 4.0.0. >>>>>> [41644.512374] reiser4[mount(3109)]: traverse_tree >>>>>> >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>>>> [41644.512380] WARNING: not found on internal node: level: 6, >>>> lock_level: >>>>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>>>> [41644.512395] reiser4[mount(3109)]: key_warning >>>>>> >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>>>> [41644.512400] WARNING: Error for inode 42 (-2) >>>>>> [44813.457093] reiser4: sdc: found disk format 4.0.0. >>>>>> [44923.248153] reiser4[mount(13238)]: traverse_tree >>>>>> >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>>>> [44923.248158] WARNING: not found on internal node: level: 6, >>>> lock_level: >>>>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>>>> [44923.248173] reiser4[mount(13238)]: key_warning >>>>>> >>>> >> (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>>>> [44923.248178] WARNING: Error for inode 42 (-2) >>>>>> >>>>> >>>>> Looks like stat-data of root inode can not be found at mount time. >>>>> Could you please run fsck.reiser4 --check /dev/sdc and send the >> output? >>>>> >>>>> Thanks, >>>>> Edward. >>>> Hello, >>>> I run the command [it took some time] and the result was as follows: >>>> # fsck.reiser4 --check /dev/sdc >>>> ******************************************************************* >>>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first. >>>> ******************************************************************* >>>> >>>> Fscking the /dev/sdc block device. >>>> >>>> Will check the consistency of the Reiser4 SuperBlock. >>>> >>>> Will check the consistency of the Reiser4 FileSystem. >>>> >>>> Continue? >>>> >>>> (Yes/No): yes >>>> ***** fsck.reiser4 started at Mon Jan 30 23:10:17 2012 >>>> Reiser4 fs was detected on /dev/sdc. >>>> >>>> Master super block (16): >>>> magic: ReIsEr4 >>>> blksize: 4096 >>>> format: 0x0 (format40) >>>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede >>>> label:<none> >>>> >>>> Format super block (17): >>>> plugin: format40 >>>> description: Disk-format plugin. >>>> version: 0 >>>> magic: ReIsEr40FoRmAt >>>> mkfs id: 0x1ddaf754 >>>> flushes: 0 >>>> blocks: 488378640 >>>> free blocks: 217146980 >>>> root block: 37017218 >>>> tail policy: 0x2 (smart) >>>> next oid: 0xedade >>>> file count: 188313 >>>> tree height: 6 >>>> key policy: LARGE >>>> >>>> >>>> CHECKING THE STORAGE TREE >>>> >>>> Read nodes 197008413 >>>> >>>> Nodes left in the tree 197008413 >>>> Leaves of them 194764277, Twigs of them 2217790 >>>> Time interval: Mon Jan 30 23:12:14 2012 - Tue Jan 31 07:48:37 >>>> 2012 >>>> >>>> CHECKING EXTENT REGIONS. >>>> >>>> Read twigs 2217790 >>>> >>>> Time interval: Tue Jan 31 07:48:37 2012 - Tue Jan 31 09:58:54 >>>> 2012 >>>> >>>> CHECKING THE SEMANTIC TREE >>>> >>>> FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize >> the >>>> plugin for the directory [29:0:2a]. >>>> FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory >>>> opened. >>>> Time interval: Tue Jan 31 09:58:54 2012 - Tue Jan 31 09:58:54 >>>> 2012 >>>> >>>> FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and >>>> really >>>> used block bitmap differ. >>>> ***** fsck.reiser4 finished at Tue Jan 31 09:58:54 2012 >>>> Closing fs...done >>>> >>>> 2 fatal corruptions were detected in FileSystem. Run with --build-fs >>>> option to fix them. >>> >>> >>> Ok, thanks, >>> >>> now please, run "fsck.reiser4 --build-fs /dev/sdc", >>> and after its completion run "fsck.reiser4 --check /dev/sdc" again, >>> then send the both outputs. >>> >>> Edward. >>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe >> reiserfs-devel" >>> in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Hello, >> Content of # fsck.reiser4 --build-fs /dev/sdc >> ******************************************************************* >> This is an EXPERIMENTAL version of fsck.reiser4. Read README first. >> ******************************************************************* >> >> Fscking the /dev/sdc block device. >> >> Will check the consistency of the Reiser4 SuperBlock. >> >> Will build the Reiser4 FileSystem. >> >> Continue? >> >> (Yes/No): yes >> ***** fsck.reiser4 started at Tue Jan 31 12:48:54 2012 >> Reiser4 fs was detected on /dev/sdc. >> >> Master super block (16): >> magic: ReIsEr4 >> blksize: 4096 >> >> format: 0x0 (format40) >> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede >> label:<none> >> >> Format super block (17): >> plugin: format40 >> description: Disk-format plugin. >> version: 0 >> magic: ReIsEr40FoRmAt >> mkfs id: 0x1ddaf754 >> flushes: 0 >> blocks: 488378640 >> free blocks: 217146980 >> root block: 37017218 >> tail policy: 0x2 (smart) >> next oid: 0xedade >> file count: 188313 >> tree height: 6 >> key policy: LARGE >> >> >> CHECKING THE STORAGE TREE >> >> Read nodes 197008413 >> >> Nodes left in the tree 197008413 >> Leaves of them 194764277, Twigs of them 2217790 >> Time interval: Tue Jan 31 12:50:54 2012 - Tue Jan 31 21:23:12 >> 2012 >> >> CHECKING EXTENT REGIONS. >> >> Read twigs 2217790 >> >> Time interval: Tue Jan 31 21:23:12 2012 - Tue Jan 31 23:33:35 >> 2012 >> >> LOOKING FOR UNCONNECTED NODES >> >> FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) >> and >> (1): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79) >> and (80): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24) >> and (25): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73) >> and (74): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (116595727), items (20) >> and (21): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) >> and (23): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) >> and (62): Wrong order of keys. >> Read nodes 1481038 >> >> Good nodes 471512 >> Leaves of them 466164, Twigs of them 5348 >> Time interval: Tue Jan 31 23:33:53 2012 - Tue Jan 31 23:37:46 >> 2012 >> >> ***** fsck.reiser4 finished at Tue Jan 31 23:37:46 2012 >> Closing fs...done >> >> FS is consistent. >> >> - Next step fsck.reiser4 --check /dev/sdc > > Please, don't mount the fs and send the outputs > of "fsck.reiser4 --check /dev/sdc" > > Edward. Hello I run the command and got the following output. What is the next step ? -Glenn # fsck.reiser4 --check /dev/sdc ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdc block device. Will check the consistency of the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): yes ***** fsck.reiser4 started at Wed Feb 1 00:46:45 2012 Reiser4 fs was detected on /dev/sdc. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede label: <none> Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x1ddaf754 flushes: 0 blocks: 488378640 free blocks: 217146980 root block: 37017218 tail policy: 0x2 (smart) next oid: 0xedade file count: 188313 tree height: 6 key policy: LARGE CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree 197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval: Wed Feb 1 00:48:41 2012 - Wed Feb 1 09:23:33 2012 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Wed Feb 1 09:23:33 2012 - Wed Feb 1 11:33:50 2012 CHECKING THE SEMANTIC TREE FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the plugin for the directory [29:0:2a]. FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory opened. Time interval: Wed Feb 1 11:33:50 2012 - Wed Feb 1 11:33:50 2012 FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really used block bitmap differ. ***** fsck.reiser4 finished at Wed Feb 1 11:33:51 2012 Closing fs...done 2 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-02-01 1:16 ` doiggl @ 2012-02-01 16:20 ` doiggl 2012-02-01 16:44 ` Edward Shishkin 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-02-01 16:20 UTC (permalink / raw) To: reiserfs-devel On Wed, 01 Feb 2012 12:16:10 +1100, <doiggl@velocitynet.com.au> wrote: > On Tue, 31 Jan 2012 14:55:06 +0100, Edward Shishkin > <edward.shishkin@gmail.com> wrote: >> On 01/31/2012 01:44 PM, doiggl@velocitynet.com.au wrote: >>> On Tue, 31 Jan 2012 08:50:26 +0100, Edward Shishkin >>> <edward.shishkin@gmail.com> wrote: >>>> On 01/31/2012 02:06 AM, doiggl@velocitynet.com.au wrote: >>>>> On Sun, 29 Jan 2012 16:24:11 +0100, Edward Shishkin >>>>> <edward.shishkin@gmail.com> wrote: >>>>>> On 01/29/2012 02:35 PM, doiggl@velocitynet.com.au wrote: >>>>>>> On Sun, 29 Jan 2012 08:51:53 +0100, Jonáš >>>>> Vidra<vidra.jonas@seznam.cz> >>>>>>> wrote: >>>>>>>> Dne Sun, 29 Jan 2012 05:15:48 +0100<doiggl@velocitynet.com.au> >>>>>>> napsal(a): >>>>>>>> >>>>>>>>> Hello, >>>>>>>>> I did a repair on a reiser4 partition as follows: >>>>>>>>> # fsck.reiser4 --build-fs /dev/sdc >>>>>>>>> >>>>>>>>> … >>>>>>>>> >>>>>>>>> # mount /dev/sdc /media/disk2 >>>>>>>>> mount: No such file or directory >>>>>>>>> >>>>>>>>> This did not work either >>>>>>>>> mount -t reiser4 /dev/sdc /media/disk2 >>>>>>>>> mount: No such file or directory >>>>>>>>> >>>>>>>>> Other details >>>>>>>>> ------------- >>>>>>>>> # cd /media >>>>>>>>> # md disk2 >>>>>>>>> # ll >>>>>>>>> total 3 >>>>>>>>> drwxr-xr-x 79 root root 2520 Jan 24 01:20 disk >>>>>>>>> drwxr-xr-x 2 root root 40 Jan 29 14:01 disk2 >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I suppose "md" is an alias for mkdir, right? And "ll" for ls -l? > Did >>>>> the >>>>>>>> directory /media/disk2 exist at the time you were trying to mount > to >>>>> it? >>>>>>>> Does your syslog contain anything useful? >>>>>>> Hello >>>>>>> Did the directory /media/disk2 exist at the time you were trying to >>>>> mount >>>>>>> to it? Yes >>>>>>> >>>>>>> Does your syslog contain anything useful? >>>>>>> # dmesg contans the following warnings: >>>>>>> [41535.199439] Loading Reiser4. See www.namesys.com for a > description >>>>> of >>>>>>> Reiser4. >>>>>>> [41535.205895] reiser4: sdc: found disk format 4.0.0. >>>>>>> [41644.512374] reiser4[mount(3109)]: traverse_tree >>>>>>> >>>>> >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>>>>> [41644.512380] WARNING: not found on internal node: level: 6, >>>>> lock_level: >>>>>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>>>>> [41644.512395] reiser4[mount(3109)]: key_warning >>>>>>> >>>>> >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>>>>> [41644.512400] WARNING: Error for inode 42 (-2) >>>>>>> [44813.457093] reiser4: sdc: found disk format 4.0.0. >>>>>>> [44923.248153] reiser4[mount(13238)]: traverse_tree >>>>>>> >>>>> >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/search.c:725)[nikita-373]: >>>>>>> [44923.248158] WARNING: not found on internal node: level: 6, >>>>> lock_level: >>>>>>> 1, stop_level: 1 lock_mode: read, bias: exact >>>>>>> [44923.248173] reiser4[mount(13238)]: key_warning >>>>>>> >>>>> >>> > (/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0/fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: >>>>>>> [44923.248178] WARNING: Error for inode 42 (-2) >>>>>>> >>>>>> >>>>>> Looks like stat-data of root inode can not be found at mount time. >>>>>> Could you please run fsck.reiser4 --check /dev/sdc and send the >>> output? >>>>>> >>>>>> Thanks, >>>>>> Edward. >>>>> Hello, >>>>> I run the command [it took some time] and the result was as follows: >>>>> # fsck.reiser4 --check /dev/sdc >>>>> ******************************************************************* >>>>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first. >>>>> ******************************************************************* >>>>> >>>>> Fscking the /dev/sdc block device. >>>>> >>>>> Will check the consistency of the Reiser4 SuperBlock. >>>>> >>>>> Will check the consistency of the Reiser4 FileSystem. >>>>> >>>>> Continue? >>>>> >>>>> (Yes/No): yes >>>>> ***** fsck.reiser4 started at Mon Jan 30 23:10:17 2012 >>>>> Reiser4 fs was detected on /dev/sdc. >>>>> >>>>> Master super block (16): >>>>> magic: ReIsEr4 >>>>> blksize: 4096 >>>>> format: 0x0 (format40) >>>>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede >>>>> label:<none> >>>>> >>>>> Format super block (17): >>>>> plugin: format40 >>>>> description: Disk-format plugin. >>>>> version: 0 >>>>> magic: ReIsEr40FoRmAt >>>>> mkfs id: 0x1ddaf754 >>>>> flushes: 0 >>>>> blocks: 488378640 >>>>> free blocks: 217146980 >>>>> root block: 37017218 >>>>> tail policy: 0x2 (smart) >>>>> next oid: 0xedade >>>>> file count: 188313 >>>>> tree height: 6 >>>>> key policy: LARGE >>>>> >>>>> >>>>> CHECKING THE STORAGE TREE >>>>> >>>>> Read nodes 197008413 >>>>> >>>>> Nodes left in the tree 197008413 >>>>> Leaves of them 194764277, Twigs of them 2217790 >>>>> Time interval: Mon Jan 30 23:12:14 2012 - Tue Jan 31 > 07:48:37 >>>>> 2012 >>>>> >>>>> CHECKING EXTENT REGIONS. >>>>> >>>>> Read twigs 2217790 >>>>> >>>>> Time interval: Tue Jan 31 07:48:37 2012 - Tue Jan 31 > 09:58:54 >>>>> 2012 >>>>> >>>>> CHECKING THE SEMANTIC TREE >>>>> >>>>> FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize >>> the >>>>> plugin for the directory [29:0:2a]. >>>>> FSCK: semantic.c: 651: repair_semantic_root_prepare: No root > directory >>>>> opened. >>>>> Time interval: Tue Jan 31 09:58:54 2012 - Tue Jan 31 > 09:58:54 >>>>> 2012 >>>>> >>>>> FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and >>>>> really >>>>> used block bitmap differ. >>>>> ***** fsck.reiser4 finished at Tue Jan 31 09:58:54 2012 >>>>> Closing fs...done >>>>> >>>>> 2 fatal corruptions were detected in FileSystem. Run with --build-fs >>>>> option to fix them. >>>> >>>> >>>> Ok, thanks, >>>> >>>> now please, run "fsck.reiser4 --build-fs /dev/sdc", >>>> and after its completion run "fsck.reiser4 --check /dev/sdc" again, >>>> then send the both outputs. >>>> >>>> Edward. >>>> >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe >>> reiserfs-devel" >>>> in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> Hello, >>> Content of # fsck.reiser4 --build-fs /dev/sdc >>> ******************************************************************* >>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first. >>> ******************************************************************* >>> >>> Fscking the /dev/sdc block device. >>> >>> Will check the consistency of the Reiser4 SuperBlock. >>> >>> Will build the Reiser4 FileSystem. >>> >>> Continue? >>> >>> (Yes/No): yes >>> ***** fsck.reiser4 started at Tue Jan 31 12:48:54 2012 >>> Reiser4 fs was detected on /dev/sdc. >>> >>> Master super block (16): >>> magic: ReIsEr4 >>> blksize: 4096 >>> >>> format: 0x0 (format40) >>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede >>> label:<none> >>> >>> Format super block (17): >>> plugin: format40 >>> description: Disk-format plugin. >>> version: 0 >>> magic: ReIsEr40FoRmAt >>> mkfs id: 0x1ddaf754 >>> flushes: 0 >>> blocks: 488378640 >>> free blocks: 217146980 >>> root block: 37017218 >>> tail policy: 0x2 (smart) >>> next oid: 0xedade >>> file count: 188313 >>> tree height: 6 >>> key policy: LARGE >>> >>> >>> CHECKING THE STORAGE TREE >>> >>> Read nodes 197008413 >>> >>> Nodes left in the tree 197008413 >>> Leaves of them 194764277, Twigs of them 2217790 >>> Time interval: Tue Jan 31 12:50:54 2012 - Tue Jan 31 21:23:12 >>> 2012 >>> >>> CHECKING EXTENT REGIONS. >>> >>> Read twigs 2217790 >>> >>> Time interval: Tue Jan 31 21:23:12 2012 - Tue Jan 31 23:33:35 >>> 2012 >>> >>> LOOKING FOR UNCONNECTED NODES >>> >>> FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) >>> and >>> (1): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79) >>> and (80): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24) >>> and (25): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73) >>> and (74): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (116595727), items > (20) >>> and (21): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (227923161), items > (22) >>> and (23): Wrong order of keys. >>> FSCK: node.c: 108: repair_node_items_check: Node (284305753), items > (61) >>> and (62): Wrong order of keys. >>> Read nodes 1481038 >>> >>> Good nodes 471512 >>> Leaves of them 466164, Twigs of them 5348 >>> Time interval: Tue Jan 31 23:33:53 2012 - Tue Jan 31 23:37:46 >>> 2012 >>> >>> ***** fsck.reiser4 finished at Tue Jan 31 23:37:46 2012 >>> Closing fs...done >>> >>> FS is consistent. >>> >>> - Next step fsck.reiser4 --check /dev/sdc >> >> Please, don't mount the fs and send the outputs >> of "fsck.reiser4 --check /dev/sdc" >> >> Edward. > > Hello > I run the command and got the following output. > What is the next step ? -Glenn > # fsck.reiser4 --check /dev/sdc > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/sdc block device. > > Will check the consistency of the Reiser4 SuperBlock. > > Will check the consistency of the Reiser4 FileSystem. > > Continue? > > (Yes/No): yes > ***** fsck.reiser4 started at Wed Feb 1 00:46:45 2012 > Reiser4 fs was detected on /dev/sdc. > > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format plugin. > version: 0 > magic: ReIsEr40FoRmAt > mkfs id: 0x1ddaf754 > flushes: 0 > blocks: 488378640 > free blocks: 217146980 > root block: 37017218 > tail policy: 0x2 (smart) > next oid: 0xedade > file count: 188313 > tree height: 6 > key policy: LARGE > > > CHECKING THE STORAGE TREE > > Read nodes 197008413 > > Nodes left in the tree 197008413 > Leaves of them 194764277, Twigs of them 2217790 > Time interval: Wed Feb 1 00:48:41 2012 - Wed Feb 1 09:23:33 2012 > > CHECKING EXTENT REGIONS. > > Read twigs 2217790 > > Time interval: Wed Feb 1 09:23:33 2012 - Wed Feb 1 11:33:50 2012 > > CHECKING THE SEMANTIC TREE > > FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the > plugin for the directory [29:0:2a]. > FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory > opened. > Time interval: Wed Feb 1 11:33:50 2012 - Wed Feb 1 11:33:50 2012 > > FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really > used block bitmap differ. > ***** fsck.reiser4 finished at Wed Feb 1 11:33:51 2012 > Closing fs...done > > 2 fatal corruptions were detected in FileSystem. Run with --build-fs > option to fix them. ########################## Hello I rerun the build again and got this result: # fsck.reiser4 --build-fs /dev/sdc ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdc block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): yes ***** fsck.reiser4 started at Wed Feb 1 12:20:51 2012 Reiser4 fs was detected on /dev/sdc. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede label: <none> Format super block (17): plugin: format40 description: Disk-format plugin. version: 0 magic: ReIsEr40FoRmAt mkfs id: 0x1ddaf754 flushes: 0 blocks: 488378640 free blocks: 217146980 root block: 37017218 tail policy: 0x2 (smart) next oid: 0xedade file count: 188313 tree height: 6 key policy: LARGE CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree 197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval: Wed Feb 1 12:22:49 2012 - Wed Feb 1 20:56:53 2012 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Wed Feb 1 20:56:53 2012 - Wed Feb 1 23:07:13 2012 LOOKING FOR UNCONNECTED NODES FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) and (1): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79) and (80): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24) and (25): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73) and (74): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (116595727), items (20) and (21): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) and (23): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) and (62): Wrong order of keys. Read nodes 1481038 Good nodes 471512 Leaves of them 466164, Twigs of them 5348 Time interval: Wed Feb 1 23:07:28 2012 - Wed Feb 1 23:11:16 2012 ***** fsck.reiser4 finished at Wed Feb 1 23:11:16 2012 Closing fs...done FS is consistent. Question: Do I keep running these 2 commands till something happens ??? 1. # fsck.reiser4 --check /dev/sdc 2. # fsck.reiser4 --build-fs /dev/sdc Thanks glenn -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-02-01 16:20 ` doiggl @ 2012-02-01 16:44 ` Edward Shishkin 2012-02-04 14:12 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: Edward Shishkin @ 2012-02-01 16:44 UTC (permalink / raw) To: doiggl; +Cc: reiserfs-devel On 02/01/2012 05:20 PM, doiggl@velocitynet.com.au wrote: [...] > FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) > and (23): Wrong order of keys. > FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) > and (62): Wrong order of keys. > Read nodes 1481038 > > Good nodes 471512 > Leaves of them 466164, Twigs of them 5348 > Time interval: Wed Feb 1 23:07:28 2012 - Wed Feb 1 23:11:16 2012 > > ***** fsck.reiser4 finished at Wed Feb 1 23:11:16 2012 > Closing fs...done > > FS is consistent. > > Question: > Do I keep running these 2 commands till something happens ??? > 1. # fsck.reiser4 --check /dev/sdc > 2. # fsck.reiser4 --build-fs /dev/sdc > Thanks glenn Hello. You have encountered a bug in fsck: it doesn't repair your corruption for unknown reasons. Could you please pack the metadata by debugfs.reiser4 -P /dev/xxx | gzip > meta.gz and let me download the file meta.gz I'll take a look at this at leisure, but unfortunately I can not promise a quick fixup. Thanks, Edward. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-02-01 16:44 ` Edward Shishkin @ 2012-02-04 14:12 ` doiggl 2012-02-04 15:13 ` Edward Shishkin 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-02-04 14:12 UTC (permalink / raw) To: reiserfs-devel On Wed, 01 Feb 2012 17:44:14 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 02/01/2012 05:20 PM, doiggl@velocitynet.com.au wrote: > > [...] > >> FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) >> and (23): Wrong order of keys. >> FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) >> and (62): Wrong order of keys. >> Read nodes 1481038 >> >> Good nodes 471512 >> Leaves of them 466164, Twigs of them 5348 >> Time interval: Wed Feb 1 23:07:28 2012 - Wed Feb 1 23:11:16 >> 2012 >> >> ***** fsck.reiser4 finished at Wed Feb 1 23:11:16 2012 >> Closing fs...done >> >> FS is consistent. >> >> Question: >> Do I keep running these 2 commands till something happens ??? >> 1. # fsck.reiser4 --check /dev/sdc >> 2. # fsck.reiser4 --build-fs /dev/sdc >> Thanks glenn > > > Hello. > You have encountered a bug in fsck: it doesn't repair your > corruption for unknown reasons. > > Could you please pack the metadata by > debugfs.reiser4 -P /dev/xxx | gzip > meta.gz > and let me download the file meta.gz > > I'll take a look at this at leisure, but unfortunately I > can not promise a quick fixup. > > Thanks, > Edward. Hello, I am just trying to to find a free file sharing service to share as the file its on the large side, I am still looking. If there are any free sites file to handle large files, that would be handy to know. It looks like it will a long time to upload once a transfer site site is found. Glenn File details 3,133,918,605 meta.gz # md5sum meta.gz 41c2ad7cf10c90fa73a287d1f2ddaef3 meta.gz ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-02-04 14:12 ` doiggl @ 2012-02-04 15:13 ` Edward Shishkin 2012-03-09 2:59 ` doiggl 0 siblings, 1 reply; 14+ messages in thread From: Edward Shishkin @ 2012-02-04 15:13 UTC (permalink / raw) To: doiggl, ReiserFS Development List On 02/04/2012 03:12 PM, doiggl@velocitynet.com.au wrote: [...] > Hello, > I am just trying to to find a free file sharing service to share as the > file its on the large side, I am still looking. > If there are any free sites file to handle large files, that would be > handy to know. > It looks like it will a long time to upload once a transfer site site is > found. > Glenn > > File details > 3,133,918,605 meta.gz > Again, please, don't use large volumes. There is no production support team for reiser4. The smaller volumes, the more chances that things will be fixed. Edward. > # md5sum meta.gz > 41c2ad7cf10c90fa73a287d1f2ddaef3 meta.gz ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-02-04 15:13 ` Edward Shishkin @ 2012-03-09 2:59 ` doiggl 2012-03-09 19:05 ` Edward Shishkin 0 siblings, 1 reply; 14+ messages in thread From: doiggl @ 2012-03-09 2:59 UTC (permalink / raw) To: ReiserFS Development List On Sat, 04 Feb 2012 16:13:04 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 02/04/2012 03:12 PM, doiggl@velocitynet.com.au wrote: > > [...] > >> Hello, >> I am just trying to to find a free file sharing service to share as the >> file its on the large side, I am still looking. >> If there are any free sites file to handle large files, that would be >> handy to know. >> It looks like it will a long time to upload once a transfer site site is >> found. >> Glenn >> >> File details >> 3,133,918,605 meta.gz >> > > > Again, please, don't use large volumes. > There is no production support team for reiser4. > The smaller volumes, the more chances that things will > be fixed. > > Edward. > > >> # md5sum meta.gz >> 41c2ad7cf10c90fa73a287d1f2ddaef3 meta.gz Hello, I found a site so you can access the files from [1] [1] Here is a link to the meta data files http://www.4shared.com/account/dir/mL9KC7l1/_online.html?rnd=10 Files: xaa 1,536,000 KB File xab 1,524,467 KB File To join it up for use: #cat xaa xab> meta.gz It seems a lot of meta data. Does the meta.gz show any problems ? Cheers Glenn ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc 2012-03-09 2:59 ` doiggl @ 2012-03-09 19:05 ` Edward Shishkin 0 siblings, 0 replies; 14+ messages in thread From: Edward Shishkin @ 2012-03-09 19:05 UTC (permalink / raw) To: doiggl; +Cc: ReiserFS Development List On 03/09/2012 03:59 AM, doiggl@velocitynet.com.au wrote: > On Sat, 04 Feb 2012 16:13:04 +0100, Edward Shishkin > <edward.shishkin@gmail.com> wrote: >> On 02/04/2012 03:12 PM, doiggl@velocitynet.com.au wrote: >> >> [...] >> >>> Hello, >>> I am just trying to to find a free file sharing service to share as the >>> file its on the large side, I am still looking. >>> If there are any free sites file to handle large files, that would be >>> handy to know. >>> It looks like it will a long time to upload once a transfer site site > is >>> found. >>> Glenn >>> >>> File details >>> 3,133,918,605 meta.gz >>> >> >> >> Again, please, don't use large volumes. >> There is no production support team for reiser4. >> The smaller volumes, the more chances that things will >> be fixed. >> >> Edward. >> >> >>> # md5sum meta.gz >>> 41c2ad7cf10c90fa73a287d1f2ddaef3 meta.gz > > Hello, > I found a site so you can access the files from [1] > > [1] > Here is a link to the meta data files > http://www.4shared.com/account/dir/mL9KC7l1/_online.html?rnd=10 > > Files: > xaa 1,536,000 KB File > xab 1,524,467 KB File > > To join it up for use: > #cat xaa xab> meta.gz > > It seems a lot of meta data. > Does the meta.gz show any problems ? Thanks. The unpacked file is larger than free spaces on all my partitions. So, wait.. Edward. ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2012-03-09 19:05 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-29 4:15 command 'mount /dev/sdc /media/disk2' failed after fsck.reiser4 --build-fs /dev/sdc doiggl
2012-01-29 7:51 ` Jonáš Vidra
2012-01-29 13:35 ` doiggl
2012-01-29 15:24 ` Edward Shishkin
2012-01-31 1:06 ` doiggl
2012-01-31 7:50 ` Edward Shishkin
2012-01-31 12:44 ` doiggl
[not found] ` <4F27F2BA.8090300@gmail.com>
2012-02-01 1:16 ` doiggl
2012-02-01 16:20 ` doiggl
2012-02-01 16:44 ` Edward Shishkin
2012-02-04 14:12 ` doiggl
2012-02-04 15:13 ` Edward Shishkin
2012-03-09 2:59 ` doiggl
2012-03-09 19:05 ` Edward Shishkin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).