1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SL + ReiserFS = happy Samba

Discussion in 'HyperWRT Firmware' started by vincentfox, Mar 21, 2006.

  1. vincentfox

    vincentfox Network Guru Member

    Howdy folks,

    Finally got around to trying out the HyperWRT Thibor 14 on my SL.

    Nice work!

    I particularly like the SSH settings dialogs, that's something other firmware need because you don't know HOW many times I've had to answer that same damned question about how to setup WAN SSH access, and how to change it to a non-default port. Nice that it defaults to something other than 22 for remote.

    Unfortunately, the Storage interface is the Linksys one. If I had to give Linksys a grade in a UI class, it would be a C minus. Functional but very awkward.

    I loaded it mainly to check out the ReiserFS and Samba functionality. Sure enough Reiser is there (cat /proc/filesystems) and works, sorta.

    Went to command line, fdisk the drive. Made a type 83 linux partition and ran mkreiserfs. Unfortunately the boot scripts are not able to recognize and automount this. In fact looks like they look for vfat, ntfs, and iso9660 on boot. So out of the box it won't automount your fresh new Reiser disk.

    Anyhow, I manually mounted my flash with:
    mkdir /foreign_shares/FLASH
    mount /dev/scsi/host1/bus0/target0/lun0/part1 /foreign_shares/FLASH

    At that point the volume shows up fine in Storage pages. It even shows "reiserfs" in the column for File System. I shared it, mapped it, and copied an 850 meg file to it, absolutely no problems. So it looks like everything is almost in place for using Reiser for storage. I am not really familiar enough with this firmware to say where the Reiser recognition should be added.
     
  2. vincentfox

    vincentfox Network Guru Member

    I should add that something is maybe farked with regards to my VLAN setup on loading Thibor 14. It looks like the nvram variables got reset to values appropriate for the old 54G/GS series which have only 2 ethernet ports. The SL has 3, with eth1 for the WAN. I noticed immediately that WAN was not functioning. I flashed back to OpenWRT, same problem. I wish I had backed up my nvram contents now, trying to untangle what it ought to look like.
     
  3. Thibor

    Thibor Super Moderator Staff Member Member

    wan_ifname=eth1
    wan_iface=eth1
    wan_ifnames=eth1
    lan_ifname=br0
    lan_ifnames=eth0 eth2 eth3 eth4
    wl_ifname=eth2
     
  4. vincentfox

    vincentfox Network Guru Member

    It's probably because my SL has been such a slut with different firmwares parading back and forth through the bedroom.

    I did both factory-resets from the HyperWRT admin pages, and that seemed to clear things up. Functional again.

    Thanks Thibor.
     
  5. vincentfox

    vincentfox Network Guru Member

    If I had another drive it'd be fun to play with mkraid program.

    There's also mkswap and swapon.

    Obvously our boy Barry and/or Linksys had some bigger ideas for the box than what actually got enabled in the shipped interface.

    I have to add though, that there is going to be a mild incompatibility problem for the sluts among us.

    Namely, HyperWRT has Reiser, and OpenWRT has EXT3. But neither at the moment has any crossover format except *gag* FAT.

    Nothing I can't work around, but I wish the mysterious Barry had left EXT3 in as his hidden format instead of Reiser. Nothing against Reiser it just seems like an odd choice. I know when I ran a Squid server then Reiser was *the* choice, but it's not commonly used otherwise. As far as I know it has no special advantage for flash.
     
  6. meq123

    meq123 Network Guru Member

    vincent, 'scuse my obvious newbie-ness, but it seems you performed those CLI commands from the SL itself, including the mkreiserfs. Right?.
     
  7. meq123

    meq123 Network Guru Member

  8. netddos

    netddos Network Guru Member

    what's different from openwrt+samba 2.x combo? any performance gain?
     
  9. meq123

    meq123 Network Guru Member

    Only performance point I can give is with tofu13c and a reiserfs hard drive...

    Copied a 2GB file (2.097GB actual) took about 3 secs to pop-up the progress window, and took 11min 45 secs to complete (incl the 3 sec popup time). Resulting in a 23.8 Mb/sec avg transfer rate.

    I dont use OpenWRT and so have nothing to compare it against.
     
  10. Thibor

    Thibor Super Moderator Staff Member Member

    i'm working on adding Reiser gui support right now, should be very very simple if i'm reading correctly
     
  11. Thibor

    Thibor Super Moderator Staff Member Member

    automounting Reiserfs is working. Partition creation in the web interface is ONLY FAT32 though
     
  12. vincentfox

    vincentfox Network Guru Member

    Yes, all the command-line programs I needed, were available in HyperWRT. It's nice to be able to run fdisk, mkreiserfs, etc. all from the same device you are going to be using. However I feel like I need a symlink for that device name because /dev/scsi/(blah) just gets to be too much. I like nice short deviice names like /dev/sda

    Last time I checked it, I think the OpenWRT + Samba 2.0.10 numbers were around 2.7 megabytes/sec. Around the same speed range. Nothing to sneeze at for light home usage either way.

    The Samba-3 used in Linksys based firmware is probably going to be better for some things, but it's a real pig on RAM. I notice the nmbd process and multiple smbd processes hanging around each using 3-4 megs. Memory usage is much higher. Leaves you less room for other processes.

    Unless you're a Linux type, HyperWRT with Reiser support is probably the better choice for just simple operation. And it definitely WORKS unlike the Linksys factory firmware, which does not. If Ext3 support could be added back into the kernel though, that would be an obviously useful thing.

    Samba-4 people have plans for "embedded"configure flag for compile that will build a version that is very lightweight and good-performing on devices like this. The idea is a single-thread smbd process to do all the work, since all the multiple process stuff that is a performance win on a full PC, is just silly overhead on a tiny device. But Samba-4 is a ways off yet.

    Here's a question for y'all:

    Does the USB LED on the front of the unit do it's job properly in HyperWRT? I forgot to check and don't have the unit handy just now.
     

Share This Page