* reiser4 kernel compilation problem. @ 2013-11-21 13:01 doiggl 2013-11-23 12:13 ` dimas 0 siblings, 1 reply; 11+ messages in thread From: doiggl @ 2013-11-21 13:01 UTC (permalink / raw) To: reiserfs-devel Hello, I get this message when trying to use a reiser4 partition. # mount /dev/sdb /media/disk mount: unknown filesystem type 'reiser4' What an I missing [in the kernel build] so I can use this partition ? -Thanks Glenn Steps I have done: These paramerers are set for the kernel and it built ok, and I booted from it. CONFIG_REISER4_DEBUG=n CONFIG_REISER4_FS=m I booted the new kernel # uname -a Linux test.site 3.11.9-2.ga012288-vanilla #1 SMP Thu Nov 21 10:36:29 UTC 2013 (1602f81) x86_64 x86_64 x86_64 GNU/Linux - Full kernel build log see [1] - Built rpm are at [2] - dmesg when powering up disk with reiser4 partition. [1] reiser4/kernel build log [its a long log...] https://build.opensuse.org/build/home:doiggl/openSUSE_Factory/x86_64/kernel-reiser4/_log reiser4 build parameters set: https://build.opensuse.org/package/view_file/home:doiggl/kernel-reiser4/zreiser4parameters.txt?expand=1 [2] Built reiser4/kernels https://build.opensuse.org/package/binaries/home:doiggl/kernel-reiser4?repository=openSUSE_Factory [3]dmesg when powering up disk [ 9401.263823] usb 1-2: new high-speed USB device number 3 using ehci-pci [ 9401.400157] usb 1-2: New USB device found, idVendor=04fc, idProduct=0c25 [ 9401.400170] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 9401.400177] usb 1-2: Product: USB to Serial-ATA bridge [ 9401.400183] usb 1-2: Manufacturer: Sunplus Technology Inc. [ 9401.400188] usb 1-2: SerialNumber: ST32000542 5XW1ZMG4 [ 9401.424287] usb-storage 1-2:1.0: USB Mass Storage device detected [ 9401.424697] scsi4 : usb-storage 1-2:1.0 [ 9401.424905] usbcore: registered new interface driver usb-storage [ 9402.429827] scsi 4:0:0:0: Direct-Access ST320005 42AS PQ: 0 ANSI: 2 [ 9402.430333] sd 4:0:0:0: Attached scsi generic sg2 type 0 [ 9402.431961] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 9402.434681] sd 4:0:0:0: [sdb] Write Protect is off [ 9402.434695] sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00 [ 9402.437448] sd 4:0:0:0: [sdb] No Caching mode page found [ 9402.437461] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 9402.444950] sd 4:0:0:0: [sdb] No Caching mode page found [ 9402.444962] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 9402.464733] sdb: unknown partition table [ 9402.476864] sd 4:0:0:0: [sdb] No Caching mode page found [ 9402.476876] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 9402.476885] sd 4:0:0:0: [sdb] Attached SCSI disk #fdisk -l Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-21 13:01 reiser4 kernel compilation problem doiggl @ 2013-11-23 12:13 ` dimas 2013-11-23 8:55 ` doiggl 0 siblings, 1 reply; 11+ messages in thread From: dimas @ 2013-11-23 12:13 UTC (permalink / raw) To: reiserfs-devel firstly, why are you using unpartitioned disk, creating fs on a disk, not partition? if there is r4, and drive is 2 TB, i think, it's not camera memory or smth like that)) just create mbr/gpt partition table to avoid some potential problems. secondly, check that reiser4 module is loaded, if occasionly not - try insmod. also, you can check if r4 is listed in /proc/filesystems 2013-326 00:01 doiggl@velocitynet.com.au <doiggl@velocitynet.com.au> wrote: > Hello, > I get this message when trying to use a reiser4 partition. > > # mount /dev/sdb /media/disk > mount: unknown filesystem type 'reiser4' > > What an I missing [in the kernel build] so I can use this partition ? > -Thanks Glenn > > Steps I have done: > These paramerers are set for the kernel and it built ok, and I booted from > it. > > CONFIG_REISER4_DEBUG=n > CONFIG_REISER4_FS=m > > I booted the new kernel > # uname -a > Linux test.site 3.11.9-2.ga012288-vanilla #1 SMP Thu Nov 21 10:36:29 UTC > 2013 (1602f81) x86_64 x86_64 x86_64 GNU/Linux > > - Full kernel build log see [1] > - Built rpm are at [2] > - dmesg when powering up disk with reiser4 partition. > > [1] reiser4/kernel build log [its a long log...] > https://build.opensuse.org/build/home:doiggl/openSUSE_Factory/x86_64/kernel-reiser4/_log > > reiser4 build parameters set: > https://build.opensuse.org/package/view_file/home:doiggl/kernel-reiser4/zreiser4parameters.txt?expand=1 > > [2] Built reiser4/kernels > https://build.opensuse.org/package/binaries/home:doiggl/kernel-reiser4?repository=openSUSE_Factory > > [3]dmesg when powering up disk > [ 9401.263823] usb 1-2: new high-speed USB device number 3 using ehci-pci > [ 9401.400157] usb 1-2: New USB device found, idVendor=04fc, > idProduct=0c25 > [ 9401.400170] usb 1-2: New USB device strings: Mfr=2, Product=3, > SerialNumber=1 > [ 9401.400177] usb 1-2: Product: USB to Serial-ATA bridge > [ 9401.400183] usb 1-2: Manufacturer: Sunplus Technology Inc. > [ 9401.400188] usb 1-2: SerialNumber: ST32000542 5XW1ZMG4 > [ 9401.424287] usb-storage 1-2:1.0: USB Mass Storage device detected > [ 9401.424697] scsi4 : usb-storage 1-2:1.0 > [ 9401.424905] usbcore: registered new interface driver usb-storage > [ 9402.429827] scsi 4:0:0:0: Direct-Access ST320005 42AS > PQ: 0 ANSI: 2 > [ 9402.430333] sd 4:0:0:0: Attached scsi generic sg2 type 0 > [ 9402.431961] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 > TB/1.81 TiB) > [ 9402.434681] sd 4:0:0:0: [sdb] Write Protect is off > [ 9402.434695] sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00 > [ 9402.437448] sd 4:0:0:0: [sdb] No Caching mode page found > [ 9402.437461] sd 4:0:0:0: [sdb] Assuming drive cache: write through > [ 9402.444950] sd 4:0:0:0: [sdb] No Caching mode page found > [ 9402.444962] sd 4:0:0:0: [sdb] Assuming drive cache: write through > [ 9402.464733] sdb: unknown partition table > [ 9402.476864] sd 4:0:0:0: [sdb] No Caching mode page found > [ 9402.476876] sd 4:0:0:0: [sdb] Assuming drive cache: write through > [ 9402.476885] sd 4:0:0:0: [sdb] Attached SCSI disk > > #fdisk -l > Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 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 > > > -- > 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] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-23 12:13 ` dimas @ 2013-11-23 8:55 ` doiggl 2013-11-25 9:53 ` Nicolas Barbier 2013-11-25 9:56 ` dimas 0 siblings, 2 replies; 11+ messages in thread From: doiggl @ 2013-11-23 8:55 UTC (permalink / raw) To: reiserfs-devel On Sat, 23 Nov 2013 16:13:09 +0400, dimas <dimas000@ya.ru> wrote: > firstly, why are you using unpartitioned disk, creating fs on a disk, not > partition? if there is r4, and drive is 2 TB, i think, it's not camera > memory > or smth like that)) just create mbr/gpt partition table to avoid some > potential > problems. > secondly, check that reiser4 module is loaded, if occasionly not - try > insmod. > also, you can check if r4 is listed in /proc/filesystems > Hello, Here are the details: # insmod Usage: insmod filename [args] # ll /proc/filesystems -r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems # rpm -qa| grep -i reiser4 | sort kernel-reiser4-3.11.9-2.1.ga012288.x86_64 libreiser4-1_0-8-1.0.8-3.1.2.x86_64 reiser4progs-1.0.8-8.1.x86_64 Back to the Question: What reiser4 kernel build paramerers I need in the kernel build so I can use this partition ? I have set: CONFIG_REISER4_DEBUG=n CONFIG_REISER4_FS=m -Thanks Glenn I know its a reiser4 formatted disk, checked as follows: # time fsck.reiser4 --build-fs /dev/sdb ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/sdb block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): yes ***** fsck.reiser4 started at Sun Nov 24 17:31:49 2013 Reiser4 fs was detected on /dev/sdb. 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 Nov 24 17:33:46 2013 - Mon Nov 25 01:10:23 2013 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Mon Nov 25 01:10:23 2013 - Mon Nov 25 03:20:04 2013 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: Mon Nov 25 03:20:19 2013 - Mon Nov 25 03:23:50 2013 ***** fsck.reiser4 finished at Mon Nov 25 03:23:50 2013 Closing fs...done FS is consistent. real 592m8.770s user 48m29.548s sys 40m54.200s ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-23 8:55 ` doiggl @ 2013-11-25 9:53 ` Nicolas Barbier 2013-11-25 9:56 ` dimas 1 sibling, 0 replies; 11+ messages in thread From: Nicolas Barbier @ 2013-11-25 9:53 UTC (permalink / raw) To: doiggl; +Cc: reiserfs-devel 2013/11/23 <doiggl@velocitynet.com.au>: > Here are the details: > > # insmod > Usage: insmod filename [args] You didn’t specify a module to load. The usage help message of just “insmod” is absolutely irrelevant. First use “lsmod” (this one doesn’t need arguments :-)) to check whether the module is loaded. If not, use “insmod <modulename>” to load it. > # ll /proc/filesystems > -r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems Please look *into* this file, i.e., use “cat”, not “ll”. Nicolas -- A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- 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] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-23 8:55 ` doiggl 2013-11-25 9:53 ` Nicolas Barbier @ 2013-11-25 9:56 ` dimas 2013-11-25 11:30 ` Edward Shishkin 1 sibling, 1 reply; 11+ messages in thread From: dimas @ 2013-11-25 9:56 UTC (permalink / raw) To: reiserfs-devel > Hello, > Here are the details: > > # insmod > Usage: insmod filename [args] no-no-no, insmod is used to load module. you must give it a module name to load. also there is lsmod, which shows currently loaded modules. read man insmod, man lsmod for details. so, aftre your mount attempt (not before it, because modules usually load only when requested) check if reiser4 module did loaded: lsmod | grep "reiser4" if it occasionaly shows nothing, try loading it manually, using "insmod reiser4" or better modprobe -v reiser4 if this will fail too, there should be a problem with the module itself. i'm using no modules, building only what i need, and building it static (=Y). static built reiser4 works perfectly wirh 3.11 for me, so i don't know, what's that. check dmesg after attempt to load, maybe there is something. > # ll /proc/filesystems > -r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems try "cat /proc/filesystems")) it shows list of fs types, which kernel currently support > Back to the Question: > What reiser4 kernel build paramerers I need in the kernel build so I can > use this partition ? > I have set: > CONFIG_REISER4_DEBUG=n > CONFIG_REISER4_FS=m if you are not using cryptocompress plugin (your fsck lock says, you are not). i believe, this is enough. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-25 9:56 ` dimas @ 2013-11-25 11:30 ` Edward Shishkin 2013-11-25 15:03 ` dimas 2013-11-26 14:58 ` doiggl 0 siblings, 2 replies; 11+ messages in thread From: Edward Shishkin @ 2013-11-25 11:30 UTC (permalink / raw) To: reiserfs-devel, dimas000 On 11/25/2013 10:56 AM, dimas wrote: >> Hello, >> Here are the details: >> >> # insmod >> Usage: insmod filename [args] > no-no-no, insmod is used to load module. you must give it a module name to load. > also there is lsmod, which shows currently loaded modules. read man insmod, man > lsmod for details. > so, aftre your mount attempt (not before it, because modules usually load only > when requested) check if reiser4 module did loaded: > lsmod | grep "reiser4" > if it occasionaly shows nothing, try loading it manually, using "insmod > reiser4" or better > modprobe -v reiser4 > if this will fail too, there should be a problem with the module itself. > i'm using no modules, building only what i need, and building it static (=Y). > static built reiser4 works perfectly wirh 3.11 for me, so i don't know, what's > that. check dmesg after attempt to load, maybe there is something. > >> # ll /proc/filesystems >> -r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems > try "cat /proc/filesystems")) it shows list of fs types, which kernel currently > support > >> Back to the Question: >> What reiser4 kernel build paramerers I need in the kernel build so I can >> use this partition ? >> I have set: >> CONFIG_REISER4_DEBUG=n >> CONFIG_REISER4_FS=m > if you are not using cryptocompress plugin (your fsck lock says, you are not). > i believe, this is enough. Fsck doesn't report if compression has been enabled. debugfs.reiser4 should be patched to show value of "create" (reg40 or ccreg40), "compress" (lzo1, or gzip1), etc. Edward. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-25 11:30 ` Edward Shishkin @ 2013-11-25 15:03 ` dimas 2013-11-25 19:37 ` Edward Shishkin 2013-11-26 14:58 ` doiggl 1 sibling, 1 reply; 11+ messages in thread From: dimas @ 2013-11-25 15:03 UTC (permalink / raw) To: reiserfs-devel > Fsck doesn't report if compression has been enabled. > debugfs.reiser4 should be patched to show value of "create" (reg40 or > ccreg40), > "compress" (lzo1, or gzip1), etc. oh, didn't know, thanks! i thought that "format40" is just equal to "reg40". thus, there is currently no way to determine fs format (reg40 or ccreg40) and compression type (if any)? maybe, such information in fsck would be nice?)) ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-25 15:03 ` dimas @ 2013-11-25 19:37 ` Edward Shishkin 0 siblings, 0 replies; 11+ messages in thread From: Edward Shishkin @ 2013-11-25 19:37 UTC (permalink / raw) To: reiserfs-devel, dimas000 On 11/25/2013 04:03 PM, dimas wrote: >> Fsck doesn't report if compression has been enabled. >> debugfs.reiser4 should be patched to show value of "create" (reg40 or >> ccreg40), >> "compress" (lzo1, or gzip1), etc. > oh, didn't know, thanks! i thought that "format40" is just equal to "reg40". Not really. "format4x" is per-volume thing, whereas "reg4x" is per-directory thing. BTW, "ccreg40" is bad name: I insisted on "reg41", but reiser4progs authors were too lazy to change things... > thus, there is currently no way to determine fs format (reg40 or ccreg40) Volume format (only "format40" for now) is determined at mkfs time. "Create" value (only reg40 and ccreg40 for now) of root directory is determined at mkfs time and inherited by children. You can change "create" value of any directory (including the root one) at any time (e.g. with ioctl(2) ), so that new children will inherit that new value (not implemented). > and > compression type (if any)? maybe, such information in fsck would be nice?)) Actually, fsck is to check consistency.#0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0 exts: 3 mask: 0x13 plugin: sdext_lw offset: 2 len: 14 mode: drwxr-xr-x nlink: 4 size: 3 plugin: sdext_unix offset: 16 len: 28 uid: 0 gid: 0 atime: Mon Nov 4 21:22:24 2013 mtime: Mon Nov 4 21:13:07 2013 ctime: Mon Nov 4 21:13:07 2013 rdev: 150 bytes: 150 plugin: sdext_plugin_set offset: 44 len: 50 Pset count: 12 permission : id = 0 formatting : id = 2 (smart) hash : id = 1 (r5_hash) fibration : id = 2 (ext_1_fibre) statdata : id = 0 (stat40) diritem : id = 2 (cde40) crypto : id = 0 digest : id = 0 compress : id = 0 (lzo1) compressMode : id = 4 (conv) cluster : id = 0 (64K) create : id = 0 (reg40) There is a special tool for such needs (debugfs.reiser4). With the option -t it dumps the whole tree. You should find any stat-data item, and take a look at the "create" parameter. In the following example compression has been disabled: #0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0 exts: 3 mask: 0x13 plugin: sdext_lw offset: 2 len: 14 mode: drwxr-xr-x nlink: 4 size: 3 plugin: sdext_unix offset: 16 len: 28 uid: 0 gid: 0 atime: Mon Nov 4 21:22:24 2013 mtime: Mon Nov 4 21:13:07 2013 ctime: Mon Nov 4 21:13:07 2013 rdev: 150 bytes: 150 plugin: sdext_plugin_set offset: 44 len: 50 Pset count: 12 permission : id = 0 formatting : id = 2 (smart) hash : id = 1 (r5_hash) fibration : id = 2 (ext_1_fibre) statdata : id = 0 (stat40) diritem : id = 2 (cde40) crypto : id = 0 digest : id = 0 compress : id = 0 (lzo1) compressMode : id = 4 (conv) cluster : id = 0 (64K) create : id = 0 (reg40) ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-25 11:30 ` Edward Shishkin 2013-11-25 15:03 ` dimas @ 2013-11-26 14:58 ` doiggl 2013-11-26 21:04 ` dimas 1 sibling, 1 reply; 11+ messages in thread From: doiggl @ 2013-11-26 14:58 UTC (permalink / raw) To: Edward Shishkin; +Cc: reiserfs-devel, dimas000 On Mon, 25 Nov 2013 12:30:48 +0100, Edward Shishkin <edward.shishkin@gmail.com> wrote: > On 11/25/2013 10:56 AM, dimas wrote: >>> Hello, >>> Here are the details: >>> >>> # insmod >>> Usage: insmod filename [args] >> no-no-no, insmod is used to load module. you must give it a module name >> to load. >> also there is lsmod, which shows currently loaded modules. read man >> insmod, man >> lsmod for details. >> so, aftre your mount attempt (not before it, because modules usually >> load only >> when requested) check if reiser4 module did loaded: >> lsmod | grep "reiser4" >> if it occasionaly shows nothing, try loading it manually, using "insmod >> reiser4" or better >> modprobe -v reiser4 >> if this will fail too, there should be a problem with the module itself. >> i'm using no modules, building only what i need, and building it static >> (=Y). >> static built reiser4 works perfectly wirh 3.11 for me, so i don't know, >> what's >> that. check dmesg after attempt to load, maybe there is something. >> >>> # ll /proc/filesystems >>> -r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems >> try "cat /proc/filesystems")) it shows list of fs types, which kernel >> currently >> support >> >>> Back to the Question: >>> What reiser4 kernel build paramerers I need in the kernel build so I can >>> use this partition ? >>> I have set: >>> CONFIG_REISER4_DEBUG=n >>> CONFIG_REISER4_FS=m >> if you are not using cryptocompress plugin (your fsck lock says, you are >> not). >> i believe, this is enough. > > > Fsck doesn't report if compression has been enabled. > debugfs.reiser4 should be patched to show value of "create" (reg40 or > ccreg40), > "compress" (lzo1, or gzip1), etc. > > 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, I tried the following 7 steps. dmesg log shows key_warning [see below] What do I do mext ? Thanks Glenn 1. # cat /proc/filesystems |sort btrfs ext2 ext3 ext4 fuseblk iso9660 reiserfs nodev anon_inodefs nodev autofs nodev bdev nodev cgroup nodev cpuset nodev debugfs nodev devpts nodev devtmpfs nodev fuse nodev fusectl nodev hugetlbfs nodev mqueue nodev pipefs nodev proc nodev pstore nodev ramfs nodev rootfs nodev securityfs nodev sockfs nodev sysfs nodev tmpfs 2. # mount /dev/sdb /media/disk mount: unknown filesystem type 'reiser4 3. # insmod reiser4 insmod: can't read 'reiser4': No such file or directory 4. # modprobe -v reiser4 insmod /lib/modules/3.11.9-2.ga012288-vanilla/kernel/fs/reiser4/reiser4.ko 5. I see reiser4 in /proc/filesystems [below] # cat /proc/filesystems |sort btrfs ext2 ext3 ext4 fuseblk iso9660 reiser4 reiserfs nodev anon_inodefs nodev autofs nodev bdev nodev cgroup nodev cpuset nodev debugfs nodev devpts nodev devtmpfs nodev fuse nodev fusectl nodev hugetlbfs nodev mqueue nodev pipefs nodev proc nodev pstore nodev ramfs nodev rootfs nodev securityfs nodev sockfs nodev sysfs nodev tmpfs 6. Retried step # mount /dev/sdb /media/disk mount: mount(2) failed: No such file or directory 7. dmesg log shows: [ 1057.245719] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 1057.382157] usb 1-1: New USB device found, idVendor=04fc, idProduct=0c25 [ 1057.382171] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 1057.382178] usb 1-1: Product: USB to Serial-ATA bridge [ 1057.382184] usb 1-1: Manufacturer: Sunplus Technology Inc. [ 1057.382189] usb 1-1: SerialNumber: ST32000542 5XW1ZMG4 [ 1057.402783] usb-storage 1-1:1.0: USB Mass Storage device detected [ 1057.403048] scsi4 : usb-storage 1-1:1.0 [ 1057.403281] usbcore: registered new interface driver usb-storage [ 1058.406928] scsi 4:0:0:0: Direct-Access ST320005 42AS PQ: 0 ANSI: 2 [ 1058.407468] sd 4:0:0:0: Attached scsi generic sg2 type 0 [ 1058.413888] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 1058.416565] sd 4:0:0:0: [sdb] Write Protect is off [ 1058.416578] sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00 [ 1058.419294] sd 4:0:0:0: [sdb] No Caching mode page found [ 1058.419306] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 1058.426820] sd 4:0:0:0: [sdb] No Caching mode page found [ 1058.426834] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 1058.448674] sdb: unknown partition table [ 1058.460729] sd 4:0:0:0: [sdb] No Caching mode page found [ 1058.460743] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 1058.460751] sd 4:0:0:0: [sdb] Attached SCSI disk [ 1059.926891] SFW2-INext-DROP-DEFLT IN=enp3s0f5 OUT= MAC= SRC=fe80:0000:0000:0000:22cf:30ff:fe28:fda2 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 [ 1355.630505] Loading Reiser4. See www.namesys.com for a description of Reiser4. [ 1556.544870] CE: hpet increased min_delta_ns to 20115 nsec [ 1605.505484] reiser4: sdb: found disk format 4.0.0. [ 1716.171644] reiser4[mount(1879)]: traverse_tree (/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.11.9/linux-3.11/fs/reiser4/search.c:725)[nikita-373]: WARNING: not found on internal node: level: 6, lock_level: 1, stop_level: 1 lock_mode: read, bias: exact [ 1716.171662] reiser4[mount(1879)]: key_warning (/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.11.9/linux-3.11/fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]: WARNING: Error for inode 42 (-2) ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-26 14:58 ` doiggl @ 2013-11-26 21:04 ` dimas 2013-11-28 21:57 ` Edward Shishkin 0 siblings, 1 reply; 11+ messages in thread From: dimas @ 2013-11-26 21:04 UTC (permalink / raw) To: reiserfs-devel > 3. > # insmod reiser4 > insmod: can't read 'reiser4': No such file or directory > 4. > # modprobe -v reiser4 > insmod /lib/modules/3.11.9-2.ga012288-vanilla/kernel/fs/reiser4/reiser4.ko hm, try running "depmod -v". seems like "reiser4" is not listed in modules.dep or whereever it should be, thus insmod cannot find it (and load on mount attempt). read "man depmod" if it will ask smth more - since i don't have any modules on both machines, i can't check what options are necessary. as for those dmesg warnings - we can just see what will Edward say on this)) meanwhile i offer you the simplest way to check whether they are driver/kernel related, or your fs has error that fsck can't detect or fix - just create shiny new reiser4 fs on some free partiton or even on loop-mounted temporary file and try wirh it. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4 kernel compilation problem. 2013-11-26 21:04 ` dimas @ 2013-11-28 21:57 ` Edward Shishkin 0 siblings, 0 replies; 11+ messages in thread From: Edward Shishkin @ 2013-11-28 21:57 UTC (permalink / raw) To: reiserfs-devel, dimas000 26.11.2013 22:04, dimas пишет: >> 3. >> # insmod reiser4 >> insmod: can't read 'reiser4': No such file or directory >> 4. >> # modprobe -v reiser4 >> insmod /lib/modules/3.11.9-2.ga012288-vanilla/kernel/fs/reiser4/reiser4.ko > hm, try running "depmod -v". seems like "reiser4" is not listed in modules.dep > or whereever it should be, thus insmod cannot find it (and load on mount > attempt). read "man depmod" if it will ask smth more - since i don't have any > modules on both machines, i can't check what options are necessary. > > as for those dmesg warnings - we can just see what will Edward say on this)) Alas, I don't have enough disk space to extract metadata of 2T reiser4 partition, so owners of broken large ones are waiting for the best times... > meanwhile i offer you the simplest way to check whether they are driver/kernel > related, or your fs has error that fsck can't detect or fix - just create shiny > new reiser4 fs on some free partiton or even on loop-mounted temporary file and > try wirh it. -- 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] 11+ messages in thread
end of thread, other threads:[~2013-11-28 21:57 UTC | newest] Thread overview: 11+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-11-21 13:01 reiser4 kernel compilation problem doiggl 2013-11-23 12:13 ` dimas 2013-11-23 8:55 ` doiggl 2013-11-25 9:53 ` Nicolas Barbier 2013-11-25 9:56 ` dimas 2013-11-25 11:30 ` Edward Shishkin 2013-11-25 15:03 ` dimas 2013-11-25 19:37 ` Edward Shishkin 2013-11-26 14:58 ` doiggl 2013-11-26 21:04 ` dimas 2013-11-28 21:57 ` Edward Shishkin
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.