Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 03:31:16PM +0200, Matthias Apitz escribió: Meanwhile I did: # cp -Rp ~guru/PKGDIR/mnt # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 # chroot /mnt pkg_add vim-7.3.1314 ... # chroot /mnt pkg_info | wc -l 654 which went fine without any errors (only the normal messages about creation of users, etc.); I will test the resulting image and report back. I have transferred the image with dd(1) to a 16 marketing-GByte USB key; it boots fine in my little EeePC 900, takes around 90 secs until login: and KDE4 starts fine too, takes around 240 secs from startx to be able to start an xterm application in KDE4 desktop; i.e. it works, even from such a slow USB key which has a read performance of 1 to 17 MByte per sec, depending of the blocksize 512 or 8m; All this is only a proof of concept to prepare such USB key to boot from and reinstall from it the system on my EeePC netbook whic runs at themoment r235646 with KDE3 (which is now dropped from our ports tree). It seems that KDE4 launches a lot of application or services which I will not need, for example all these akonadi_maildir processes (see attached ps -ax output; for what they are good for? Ok, this question goes more to the kde@ mailing list. Thx matthias PID TT STATTIME COMMAND 0 - DLs 0:00.05 [kernel] 1 - ILs 0:00.02 /sbin/init -- 2 - DL 0:00.00 [sctp_iterator] 3 - DL 0:00.00 [xpt_thrd] 4 - DL 0:00.11 [pagedaemon] 5 - DL 0:00.00 [vmdaemon] 6 - DL 0:00.00 [pagezero] 7 - DL 0:00.00 [bufdaemon] 8 - DL 0:00.09 [syncer] 9 - DL 0:00.00 [vnlru] 10 - DL 0:00.00 [audit] 11 - RL 2:53.86 [idle] 12 - WL 0:02.35 [intr] 13 - DL 0:00.84 [geom] 14 - DL 0:00.05 [rand_harvestq] 15 - DL 0:00.90 [usb] 16 - DL 0:00.03 [acpi_thermal] 17 - DL 0:00.00 [softdepflush] 1391 - Ss 0:00.03 /sbin/devd 1536 - Ss 0:00.04 /usr/sbin/syslogd -s 1560 - DL 0:00.04 [md0] 1641 - Is 0:00.60 /usr/sbin/moused -p /dev/psm0 -t auto 1686 - Is 0:00.00 /usr/sbin/sshd 1689 - Ss 0:00.02 sendmail: accepting connections (sendmail) 1692 - Is 0:00.00 sendmail: Queue runner@00:30:00 for /var/spool/clientmque 1696 - Ss 0:00.05 /usr/sbin/cron -s 1796 - Is 0:19.46 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-a 1802 - Is 0:00.91 kdeinit4: kdeinit4 Running... (kdeinit4) 1803 - I0:00.60 kdeinit4: kdeinit4: klauncher --fd=8 (kdeinit4) 1805 - I0:05.90 kdeinit4: kdeinit4: kded4 (kdeinit4) 1807 - I0:00.07 /usr/local/libexec/gam_server 1811 - I0:02.99 kdeinit4: kdeinit4: kglobalaccel (kdeinit4) 1817 - I0:06.23 /usr/local/kde4/bin/knotify4 1819 - I0:02.45 kdeinit4: kdeinit4: ksmserver (kdeinit4) 1820 - I0:11.72 kwin -session 10d6114d4e60001381347192001812_1381 1824 - I0:14.72 kdeinit4: kdeinit4: plasma-desktop (kdeinit4) 1827 - I0:20.26 /usr/local/kde4/bin/akonadi_control 1828 - I0:02.79 akonadiserver 1830 - I0:03.56 /usr/local/libexec/mysqld --defaults-file=/home/guru/.loc 1838 - I0:02.07 /usr/local/kde4/bin/kuiserver 1840 - I0:00.08 kdeinit4: kdeinit4: nepomukserver (kdeinit4) 1843 - I0:04.73 kdeinit4: kdeinit4: krunner (kdeinit4) 1845 - I0:02.35 kdeinit4: kdeinit4: kmix -session 10d6114d4e6000138134736 1846 - IN 0:00.93 /usr/local/kde4/bin/nepomukservicestub nepomukstorage 1849 - I0:00.60 /usr/local/kde4/bin/nepomukcontroller -session 10d6114d4e 1852 - I0:01.04 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1853 - I0:01.07 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1854 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1855 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1856 - I0:03.81 /usr/local/kde4/bin/akonadi_archivemail_agent --identifie 1857 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_ical_r 1858 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1859 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1860 - I0:01.12 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1861 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1862 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1863 - I0:01.10 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1864 - I0:01.06 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1865 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1866 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1867 - I0:01.03 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1868 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1869 - I0:01.02
install packages with pkg_add(1) into another file system
Hello, I have prepared a boot-able USB-key (to be exactly a disk image of it) the usual way: # dd if=/dev/zero of=da0 bs=8m count=1868 # mdconfig -a -t vnode -f da0 md0 # fdisk -I md0 # fdisk -B md0 # bsdlabel -w md0s1 auto # bsdlabel -B md0s1 # bsdlabel -e md0s1 # edit the disk label and change partition a from unused to 4.2BSD # newfs /dev/md0s1a # mount /dev/md0s1a /mnt # cd /usr/src now we can install world an kernel: # make installworld DESTDIR=/mnt # make installkernel DESTDIR=/mnt KERNCONF=GENERIC INSTALL_NODEBUG=t # make distrib-dirs DESTDIR=/mnt # make distribution DESTDIR=/mnt ... I have compiled ~800 ports (Xorg and KDE4) and after this I've created packages of all the installed ports with pkg_create(1); the resulting .tgz files are all as well copied to the image into /mnt/PKGDIR. So far so good. Now I want install the packages as well into the image in /mnt. What would be the best method for this? Run pkg_add with the flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? Thanks in advance All this is with 10-CURRENT (base and ports). matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: install packages with pkg_add(1) into another file system
On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: So far so good. Now I want install the packages as well into the image in /mnt. What would be the best method for this? Run pkg_add with the flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? Thanks in advance All this is with 10-CURRENT (base and ports). pkg_add and all of the old pkgtools do not exist in 10-CURRENT anymore. Are you running a build of 10-CURRENT before they were removed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 07:58:06AM -0500, Mark Felder escribió: On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: So far so good. Now I want install the packages as well into the image in /mnt. What would be the best method for this? Run pkg_add with the flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? Thanks in advance All this is with 10-CURRENT (base and ports). pkg_add and all of the old pkgtools do not exist in 10-CURRENT anymore. Are you running a build of 10-CURRENT before they were removed? No. The r255948 was built on a clean, empty environment but with $ cat /etc/src.conf WITH_PKGTOOLS=yes matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: install packages with pkg_add(1) into another file system
On Tue, Oct 8, 2013, at 8:07, Matthias Apitz wrote: El día Tuesday, October 08, 2013 a las 07:58:06AM -0500, Mark Felder escribió: On Tue, Oct 8, 2013, at 6:16, Matthias Apitz wrote: So far so good. Now I want install the packages as well into the image in /mnt. What would be the best method for this? Run pkg_add with the flag --chroot chrootdir, or use chroot(8) directly? Or any other idea? Thanks in advance All this is with 10-CURRENT (base and ports). pkg_add and all of the old pkgtools do not exist in 10-CURRENT anymore. Are you running a build of 10-CURRENT before they were removed? No. The r255948 was built on a clean, empty environment but with $ cat /etc/src.conf WITH_PKGTOOLS=yes Ok, I won't question your needs for pkg_* as you seem to be aware of what you're doing :-) When you use pkg_* or pkg with their built-in chroot options it seems that it executes those tools within those chroots instead of setting the chroot as a destination for the installation. So if you wanted to use --chroot I think you have to make sure the packages are available inside the chroot. Perhaps there's some sort of DESTDIR option for the package installation? I've been searching but have had no luck yet. I'll ask around. It might be more reliable to do something like nullfs mount the packages into the chroot and do the installation completely within the chroot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 08:12:31AM -0500, Mark Felder escribió: No. The r255948 was built on a clean, empty environment but with $ cat /etc/src.conf WITH_PKGTOOLS=yes Ok, I won't question your needs for pkg_* as you seem to be aware of what you're doing :-) When you use pkg_* or pkg with their built-in chroot options it seems that it executes those tools within those chroots instead of setting the chroot as a destination for the installation. So if you wanted to use --chroot I think you have to make sure the packages are available inside the chroot. Perhaps there's some sort of DESTDIR option for the package installation? I've been searching but have had no luck yet. I'll ask around. It might be more reliable to do something like nullfs mount the packages into the chroot and do the installation completely within the chroot. Meanwhile I did: # cp -Rp ~guru/PKGDIR/mnt # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 # chroot /mnt pkg_add vim-7.3.1314 ... # chroot /mnt pkg_info | wc -l 654 which went fine without any errors (only the normal messages about creation of users, etc.); I will test the resulting image and report back. matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
file-descriptor file system?
What is a fdescfs file-descriptor file system? Is it still a normal part of 9.1? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ext3 file system
Hi :) is it possible to mount Linux ext3 file systems with fstab by label? Before I run mount -a /mnt/dump had the same permissions, owner and group as /mnt/archlinux has got. Is it possible to keep this? Both are Linux ext3 fs. Mounting without a label does work. root@freebsd:/usr/home/rocketmouse # cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass /dev/ad4s1b noneswapsw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1e /tmpufs rw 2 2 /dev/ad4s1f /usrufs rw 2 2 /dev/ad4s1d /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 #proc /proc procfs rw 0 0 /dev/ada0s8 /mnt/dump ext2fs rw 0 0 #/dev/label/dump /mnt/dump ext2fs rw 0 0 #/dev/label/archlinux/mnt/archlinux ext2fs rw 0 0 root@freebsd:/usr/home/rocketmouse # ls -l /mnt total 6 drwxr-xr-x 2 rocketmouse wheel 512 Jan 20 20:51 archlinux drwxrwxrwx 2 root wheel 4096 Jan 20 20:09 dump root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt drwxr-xr-x4 root wheel 512 Jan 20 20:51 mnt I still search the Internet, but had bad luck until now. If I run 'gpart show -l' I can't see what /dev archlinux is, it doesn't show Linux labels, so I need to restart and boot Linux to see at what position it is, to figure out what /dev/ada*s* archlinux is. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ext3 file system
On Sun, 20 Jan 2013, Ralf Mardorf wrote: is it possible to mount Linux ext3 file systems with fstab by label? Before I run mount -a /mnt/dump had the same permissions, owner and group as /mnt/archlinux has got. Is it possible to keep this? Both are Linux ext3 fs. Mounting without a label does work. root@freebsd:/usr/home/rocketmouse # cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass /dev/ad4s1b noneswapsw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1e /tmpufs rw 2 2 /dev/ad4s1f /usrufs rw 2 2 /dev/ad4s1d /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 #proc /proc procfs rw 0 0 /dev/ada0s8 /mnt/dump ext2fs rw 0 0 #/dev/label/dump /mnt/dump ext2fs rw 0 0 #/dev/label/archlinux/mnt/archlinux ext2fs rw 0 0 root@freebsd:/usr/home/rocketmouse # ls -l /mnt total 6 drwxr-xr-x 2 rocketmouse wheel 512 Jan 20 20:51 archlinux drwxrwxrwx 2 root wheel 4096 Jan 20 20:09 dump root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt drwxr-xr-x4 root wheel 512 Jan 20 20:51 mnt I still search the Internet, but had bad luck until now. If I run 'gpart show -l' I can't see what /dev archlinux is, it doesn't show Linux labels, so I need to restart and boot Linux to see at what position it is, to figure out what /dev/ada*s* archlinux is. 'gpart show -l' shows GPT labels, but that only works on a GPT disk. This disk is clearly MBR. If ext3 filesystem labels show up, they would be under /dev/ext2fs. See glabel(8). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ext3 file system
Ralf Mardorf ralf.mard...@rocketmail.com writes: Hi :) is it possible to mount Linux ext3 file systems with fstab by label? Before I run mount -a /mnt/dump had the same permissions, owner and group as /mnt/archlinux has got. Is it possible to keep this? Both are Linux ext3 fs. Mounting without a label does work. root@freebsd:/usr/home/rocketmouse # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass /dev/ad4s1b noneswapsw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1e /tmpufs rw 2 2 /dev/ad4s1f /usrufs rw 2 2 /dev/ad4s1d /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 #proc /proc procfs rw 0 0 /dev/ada0s8 /mnt/dump ext2fs rw 0 0 #/dev/label/dump /mnt/dump ext2fs rw 0 0 #/dev/label/archlinux/mnt/archlinux ext2fs rw 0 0 root@freebsd:/usr/home/rocketmouse # ls -l /mnt total 6 drwxr-xr-x 2 rocketmouse wheel 512 Jan 20 20:51 archlinux drwxrwxrwx 2 root wheel 4096 Jan 20 20:09 dump root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt drwxr-xr-x4 root wheel 512 Jan 20 20:51 mnt I still search the Internet, but had bad luck until now. If I run 'gpart show -l' I can't see what /dev archlinux is, it doesn't show Linux labels, so I need to restart and boot Linux to see at what position it is, to figure out what /dev/ada*s* archlinux is. You should be able to see any labels the kernel knows about with 'glabel status', but my experience is that not all labels show up. You can check ext2/3 labels with e2label from the e2fsprogs port/package. My experience is that labels in /etc/fstab work fine, but they may or may not be visible in /dev or with glabel if they are not in fstab. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
new backup server file system options
Hi all, I am building a new freebsd fileserver to use for backups, will be using 2 disk raid mirroring in a HP microserver n40l. I have gone through some of the documentation and would like to know what file systems to choose. According to the docs, ufs is suggested for the system partitions but someone on the freebsd irc channel suggested using zfs for the rootfs as well Are there any disadvantages of using zfs for the whole system rather than going with ufs for the system files and zfs for the user data? -- Kind regards, Yudi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ZFS info WAS: new backup server file system options
On Dec 21, 2012, at 7:49 AM, yudi v wrote: I am building a new freebsd fileserver to use for backups, will be using 2 disk raid mirroring in a HP microserver n40l. I have gone through some of the documentation and would like to know what file systems to choose. According to the docs, ufs is suggested for the system partitions but someone on the freebsd irc channel suggested using zfs for the rootfs as well Are there any disadvantages of using zfs for the whole system rather than going with ufs for the system files and zfs for the user data? First a disclaimer, I have been working with Solaris since 1995 and managed lots of data under ZFS, I have only been working with FreeBSD for about the past 6 months. UFS is clearly very stable and solid, but to get redundancy you need to use a separate volume manager. ZFS is a completely different way of thinking about managing storage (not just a filesystem). I prefer ZFS for a number of reasons: 1) End to end data integrity through checksums. With the advent of 1 TB plus drives, the uncorrectable error rate (typically 10^-14 or 10^-15) means that over the life of any drive you *are* now likely to run into uncorrectable errors. This means that traditional volume managers (which rely on the drive reporting an bad reads and writes) cannot detect these errors and bad data will be returned to the application. 2) Simplicity of management. Since the volume management and filesystem layers have been combined, you don't have to manage each separately. 3) Flexibility of storage. Once you build a zpool, the filesystems that reside on it share the storage of the entire zpool. This means you don't have to decide how much space to commit to a given filesystem at creation. It also means that all the filesystems residing in that one zpool share the performance of all the drives in that zpool. 4) Specific to booting off of a ZFS, if you move drives around (as I tend to do in at least one of my lab systems) the bootloader can still find the root filesystem under ZFS as it refers to it by zfs device name, not physical drive device name. Yes, you can tell the bootloader where to find root if you move it, but zfs does that automatically. 5) Zero performance penalty snapshots. The only cost to snapshots is the space necessary to hold the data. I have managed systems with over 100,000 snapshots. I am running two production, one lab, and a bunch of VBox VMs all with ZFS. The only issue I have seen is one I have also seen under Solaris with ZFS. Certain kinds of hardware layer faults will cause the zfs management tools (the zpool and zfs commands) to hang waiting on a blocking I/O that will never return. The data continuos to be available, you just can't manage the zfs infrastructure until the device issues are cleared. For example, if you remove a USB drive that hosts a mounted ZFS, then any attempt to manage that ZFS device will hang (zpool export -f zpool name hangs until a reboot). Previously I had been running (at home) a fileserver under OpenSolaris using ZFS and it saved my data when I had multiple drive failures. At a certain client we had a 45 TB configuration built on top of 120 750GB drives. We had multiple redundancy and could survive a complete failure of 2 of the 5 disk enclosures (yes, we tested this in pre-production). There are a number of good writeups on how setup a FreeBSD system to boot off of ZFS, I like this one the best http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE , but I do the zpool/zfs configuration slightly differently (based on some hard learned lessons on Solaris). I am writing up my configuration (and why I do it this way), but it is not ready yet. Make sure you look at all the information here: http://wiki.freebsd.org/ZFS , keeping in mind that lots of it was written before FreeBSD 9. I would NOT use ZFS, especially for booting, prior to release 9 of FreeBSD. Some of the reason for this is the bugs that were fixed in zpool version 28 (included in release 9). -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS info WAS: new backup server file system options
On 2012-12-21 11:28, Arthur Chance wrote: On 12/21/12 14:06, Paul Kraus wrote: On Dec 21, 2012, at 7:49 AM, yudi v wrote: I am building a new freebsd fileserver to use for backups, will be using 2 disk raid mirroring in a HP microserver n40l. I have gone through some of the documentation and would like to know what file systems to choose. According to the docs, ufs is suggested for the system partitions but someone on the freebsd irc channel suggested using zfs for the rootfs as well Are there any disadvantages of using zfs for the whole system rather than going with ufs for the system files and zfs for the user data? First a disclaimer, I have been working with Solaris since 1995 and managed lots of data under ZFS, I have only been working with FreeBSD for about the past 6 months. UFS is clearly very stable and solid, but to get redundancy you need to use a separate volume manager. Slight correction here - you don't need a volume manager (as I understand the term), you'd use the GEOM subsystem, specifically gmirror in this case. See man gmirror for details ZFS is a completely different way of thinking about managing storage (not just a filesystem). I prefer ZFS for a number of reasons: 1) End to end data integrity through checksums. With the advent of 1 TB plus drives, the uncorrectable error rate (typically 10^-14 or 10^-15) means that over the life of any drive you *are* now likely to run into uncorrectable errors. This means that traditional volume managers (which rely on the drive reporting an bad reads and writes) cannot detect these errors and bad data will be returned to the application. 2) Simplicity of management. Since the volume management and filesystem layers have been combined, you don't have to manage each separately. 3) Flexibility of storage. Once you build a zpool, the filesystems that reside on it share the storage of the entire zpool. This means you don't have to decide how much space to commit to a given filesystem at creation. It also means that all the filesystems residing in that one zpool share the performance of all the drives in that zpool. 4) Specific to booting off of a ZFS, if you move drives around (as I tend to do in at least one of my lab systems) the bootloader can still find the root filesystem under ZFS as it refers to it by zfs device name, not physical drive device name. Yes, you can tell the bootloader where to find root if you move it, but zfs does that automatically. 5) Zero performance penalty snapshots. The only cost to snapshots is the space necessary to hold the data. I have managed systems with over 100,000 snapshots. I am running two production, one lab, and a bunch of VBox VMs all with ZFS. The only issue I have seen is one I have also seen under Solaris with ZFS. Certain kinds of hardware layer faults will cause the zfs management tools (the zpool and zfs commands) to hang waiting on a blocking I/O that will never return. The data continuos to be available, you just can't manage the zfs infrastructure until the device issues are cleared. For example, if you remove a USB drive that hosts a mounted ZFS, then any attempt to manage that ZFS device will hang (zpool export -f zpool name hangs until a reboot). Previously I had been running (at home) a fileserver under OpenSolaris using ZFS and it saved my data when I had multiple drive failures. At a certain client we had a 45 TB configuration built on top of 120 750GB drives. We had multiple redundancy and could survive a complete failure of 2 of the 5 disk enclosures (yes, we tested this in pre-production). There are a number of good writeups on how setup a FreeBSD system to boot off of ZFS, I like this one the best http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE , but I do the zpool/zfs configuration slightly differently (based on some hard learned lessons on Solaris). I am writing up my configuration (and why I do it this way), but it is not ready yet. Make sure you look at all the information here: http://wiki.freebsd.org/ZFS , keeping in mind that lots of it was written before FreeBSD 9. I would NOT use ZFS, especially for booting, prior to release 9 of FreeBSD. Some of the reason for this is the bugs that were fixed in zpool version 28 (included in release 9). I would agree with all that. My current system uses UFS filesystems for the base install, and ZFS with a raidz zpool for everything else, but that's only because I started using ZFS in REL 8.0 when it was just out of experimental status, and I didn't want to risk having an unbootable system. (That last paragraph suggests I was wise in that decision.) My next machine I'm specing out now will be pure ZFS so I get the boot environment stuff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
Re: How is zfs file system known in fsck?
--On November 18, 2012 10:38:43 AM -0500 Lynn Steven Killingsworth blue.seahorse.syndic...@gmail.com wrote: Hi FreeBSD - On my PC-BSD 9.1 RC3 I need to run fsck on my internal storage drive. I would like to use I think: fsck -y -F -t ufs /dev The question is what should I place for 'ufs' since I have zfs. My guesses just generate similar to 'directories unknown' My disk is also gpt. If I leave out the file system type after -t my machine apparently accepts a command to do something, but it of course does not do what is needed. Thanks If you're going to run advanced filesystems you really should try to understand how they work. There is no fsck tool and no need for one on zfs. If you have managed to loose data while running zfs you'd better have a backup. Read zpool(8) zfs(8) and possibly http://docs.oracle.com/cd/E19253-01/819-5461/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how restore an unencrypted dump on an encrypted file system?
hi i have a similar problem too. can you explain in detail what you have done step by step? i wanna know if my problem is exactly what you have. thanks On 9/29/12, s m sam.gh1...@gmail.com wrote: thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how restore an unencrypted dump on an encrypted file system?
thanks saeedeh OK i try to explain what i have done more in detail. i want to restore unencrypted dump files on an encrypted file system. in order to do that, i encrypted my file system by geli command and sure that is done correctly because when i install base and kernel on it, freebsd start up successfully. problem is here: when i restore my dump files and restart my freebsd, boot PXE menu is shown and i select my freebsd but after that, the error message invalid format occurs and i see this message: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: it selects the default kernel correctly and after some seconds an error message is shown which consists of some hardware addresses. i don't know how to fix it. any hints that might fix my problem are appreciated. On 9/30/12, saeedeh motlagh saeedeh.motl...@gmail.com wrote: hi i have a similar problem too. can you explain in detail what you have done step by step? i wanna know if my problem is exactly what you have. thanks On 9/29/12, s m sam.gh1...@gmail.com wrote: thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how restore an unencrypted dump on an encrypted file system?
On Sun, Sep 30, 2012 at 10:09 AM, s m sam.gh1...@gmail.com wrote: thanks saeedeh OK i try to explain what i have done more in detail. i want to restore unencrypted dump files on an encrypted file system. in order to do that, i encrypted my file system by geli command and sure that is done correctly because when i install base and kernel on it, freebsd start up successfully. problem is here: when i restore my dump files and restart my freebsd, boot PXE menu is shown and i select my freebsd but after that, the error message invalid format occurs and i see this message: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: it selects the default kernel correctly and after some seconds an error message is shown which consists of some hardware addresses. i don't know how to fix it. any hints that might fix my problem are appreciated. You could try to let us know what kind of error message you get (i.e. the exact wording). ;-) My guess (out of the blue) is that kernel and modules are now out of sync. This happens when you restore the modules from backup but use a newer kernel (or vice-versa). If you restore stuff from backup, make sure you don't restore anything under your freshly (re-)installed /boot. Or make sure you restore *everything* into /boot, and not just some parts of it. /boot has to be consistent; either everything from the new install, or everything from the backup up install, but not a mix of both. As others pointed out, you need to provide more detailed infos about your backup and restore procedure. It it impossible to guess correctly what you have done otherwise. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how restore an unencrypted dump on an encrypted file system?
hello guys, I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). please let me know how i can fix it or if i do something wrong. yours, sam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how restore an unencrypted dump on an encrypted file system?
s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian signature.asc Description: PGP signature
Re: how restore an unencrypted dump on an encrypted file system?
thanks Fabian for your answer. i don't know what exactly information is needed but i tell what i did up to now. i have two partition, one is encrypted and the other one is not. the unencrypted partition has boot folder. when i copy FreeBSD base system files, FreeBSD start up correctly but when i restore dump files, FreeBSD doesn't start up correctly. i hope this information help to understand what is wrong. thanks On 9/29/12, Fabian Keil freebsd-lis...@fabiankeil.de wrote: s m sam.gh1...@gmail.com wrote: I backed up my freeBSD 8.2 box by dump command and now want to restore this dump file on an encrypted file system (i used geli to encrypt my file system) but do not know how to do that. is there any way or command to restore an unencrypted dump on an encrypted file system? i tried to restore my dump file as when file system is unencrypted. Can you read the files after attaching the provider manually? this is what i've doe: I decrypted my encrypted file system by geli attach command, then mount it and restore dumps. but when i restart my system, FreeBSD doesn't start up correctly (PXE boot menu is shown and when i select freeBSD, boot.config runs but nothing happend). You do not provide enough information to give a meaningful answer. One possible mistake would be putting the kernel itself on the encrypted file system, but the list of things one can do wrong is pretty long. Fabian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck not working on messed-up file system
* PLEASE RERUN FSCK * Script done on Wed Sep 19 04:17:27 2012 Would this indicate a software bug, or is my Western Digital Caviar Green 3 TB hard drive failing? Either something was referencing sectors off the end of the disc, or the drive is failing. I'd be inclined to copy the data off somewhere safe and subject the disc to extensive tests with smartctl from smartmontools, then if it passes recreate the fileystem(s) and restore the data. Steve O'Hara-Smith at...@sohara.org I went looking to see if there was something more powerful than fsck in the ports tree, category sysutils, but didn't find anything. I wonder why NetBSD fsck was able to revive the partition when FreeBSD fsck got stuck in a loop, though I easily got out of said loop by not re-rerunning fsck. Maybe NetBSD fsck was better than FreeBSD fsck for repairing NetBSD mischief? It might be good to build, from ports, not only smartmontools but also subversion, on my backup 8 GB FreeBSD USB stick. I might also want to rerun cvs up -dP on the NetBSD pkgsrc and system-source directories before using again, hoping to retrieve anything that might have been lost. Script started on Wed Sep 19 04:15:02 2012 fsck_ffs /dev/ada0p9 just to make sure: the partition was not mounted when you started fsck? Now I wonder if the file system is really fixed, with possibly some files in /pkgsrc subdirectories lost, or if the hard drive is starting to fail. You see it soon. I would not bother about a single problem like this. I have had it over and over again at a location with bad power supply with a normal PC without UPS. The hard disk is - one year later - still working in a different location without any new problems. Erich I remembered not to run fsck on a mounted partition. When I booted into NetBSD, I mounted the partition, /dev/dk6, and found it didn't look trashed, though there was a warning regarding the dirty flag. Then I umounted before running fsck_ffs, successfully. It was not a power problem, I have Opti-UPS. NetBSD crashed a few times with the partition in question mounted. Starting X and exiting X are high-crash-risk in NetBSD. Maybe using the same partition by both FreeBSD and NetBSD induces file system errors? Or maybe it's the NetBSD system crash. I could be sure to not have any partition on 3 TB hard disk mounted unnecessarily when running NetBSD: umount when finished and before running X. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
fsck not working on messed-up file system
I have or had a problem with a file system (FreeBSD UFS2) messed up, either by errant software or system freeze/crash. I successfully cross-compiled, from FreeBSD 9.0-STABLE, a NetBSD 5.1_STABLE i386 system to install on 8 GB USB stick. I have both the NetBSD system source as well as pkgsrc and the FreeBSD ports tree on a FreeBSD partition originally used for FreeBSD 9.0-BETA1, hence I use /BETA1 as the mount point. This partition is /dev/ada0p9 in FreeBSD and /dev/dk6 in NetBSD. I subsequently built modular-xorg for this NetBSD installation, installating to USB stick but doing the heavy compiling on the hard-drive partition. NetBSD, especially with X, is rather freeze/crash-prone, meaning file system is not cleanly umounted. I then tried to cross-compile, from same NetBSD source tree, NetBSD 5.1_STABLE amd64 but was thrown in the debugger (db), not really knowing what to do there. Choosing reset did not provide clean file-system unmount. I had to run fsck /dev/ada0p9 on the reboot, got unreadable sectors and eventually a prompt to run fsck again. I did this but got to an infinite loop, where I got the same prompt again to run fsck again, with the same unreadable blocks. I got the same thing booting a backup installation of FreeBSD 9.0_STABLE amd64 on a USB stick. I eventually ran with script to capture the output onto another USB stick, sorry about all those ASCII 13s at the ends of the lines: Script started on Wed Sep 19 04:15:02 2012 fsck_ffs /dev/ada0p9 ** /dev/ada0p9 ** Last Mounted on /BETA1 ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 7584192 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, 0.2% fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * Script done on Wed Sep 19 04:17:27 2012 Would this indicate a software bug, or is my Western Digital Caviar Green 3 TB hard drive failing? I booted that USB stick with NetBSD 5.1_STABLE i386, successfully mounted that partition, /dev/dk6 in NetBSD, but got the message about dirty flag. So I umounted and ran NetBSD fsck_ffs, and after removing some files, mainly in /pkgsrc directory, and salvaging some stuff, got apparent success, and now that file system is again accessible in both NetBSD 5.1_STABLE i386 and FreeBSD 9.0_STABLE amd64. Now I wonder if the file system is really fixed, with possibly some files in /pkgsrc subdirectories lost, or if the hard drive is starting to fail. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck not working on messed-up file system
On Wed, 19 Sep 2012 06:05:06 -0400 Thomas Mueller muelle...@insightbb.com wrote: THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, 0.2% fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * Script done on Wed Sep 19 04:17:27 2012 Would this indicate a software bug, or is my Western Digital Caviar Green 3 TB hard drive failing? Either something was referencing sectors off the end of the disc, or the drive is failing. I'd be inclined to copy the data off somewhere safe and subject the disc to extensive tests with smartctl from smartmontools, then if it passes recreate the fileystem(s) and restore the data. -- Steve O'Hara-Smith at...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck not working on messed-up file system
Hi, On Wed, 19 Sep 2012 06:05:06 -0400 Thomas Mueller muelle...@insightbb.com wrote: Script started on Wed Sep 19 04:15:02 2012 fsck_ffs /dev/ada0p9 just to make sure: the partition was not mounted when you started fsck? Now I wonder if the file system is really fixed, with possibly some files in /pkgsrc subdirectories lost, or if the hard drive is starting to fail. You see it soon. I would not bother about a single problem like this. I have had it over and over again at a location with bad power supply with a normal PC without UPS. The hard disk is - one year later - still working in a different location without any new problems. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Best file system for a busy webserver
Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? Just curious. I'm getting ready to setup a new box running FreeBSD 9, and since I'm starting from scratch, I'm questioning all my previous assumptions. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? Use stock UFS, just configure it properly. most importantly noatime. Amount of cached data is more important than hit count. Unless your webpage is incredibly bad design or constantly load different set of large amount of small file - filesystem shouldn't be a limit. Repetitive file fetches would go from cache. Just curious. I'm getting ready to setup a new box running FreeBSD 9, and since I'm starting from scratch, I'm questioning all my previous assumptions. Small files will be cached, if you push data from large set of big files that will not fit cache, make sure transfers will be fine. use 32kB block size, 4kB fragment size for UFS add options MAXPHYS=2097152 (or even twice of that) to your kernel config so there will be large transfers from disk. This tuning will not make any harm to small files. My recommendation is for serving files by WWW (or actually - by any means). If you ask for SQL database subsystem then answer is completely different: make sure all database fits memory cache, or is on SSD or it WILL BE SLOW no matter what you use. Do everything you can to limit amount of sync writes. if you use SSD and your database software allow dedicating raw partition - do it. If not - it is not crucial but useful, avoid double buffering of unix cache and database cache. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
On Thu, 16 Aug 2012 10:45:25 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? That's an average of about 3 hits per second. If it's static pages then pretty much anything will handle it easily (but please don't use FAT). If it's dynamic then the whole problem is more complex than a simple page rate. If that load is bursty it may make a difference too. Other considerations may come into play - how big is this filesystem (number of files, maximum number of entries in a directory, volume of data) ? Are there many users needing to be protected from each other ? What about archives ? snapshots ? growth ? churn ? uptime requirements, disaster recovery time ? -- Steve O'Hara-Smith | Directable Mirror Arrays C:WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
Date: Thu, 16 Aug 2012 10:45:25 -0500 From: Paul Schmehl pschmehl_li...@tx.rr.com To: FreeBSD Questions List freebsd-questions@freebsd.org Subject: Best file system for a busy webserver Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? Just curious. I'm getting ready to setup a new box running FreeBSD 9, and since I'm starting from scratch, I'm questioning all my previous assumptions. Insufficient data for a meaningful answer. A _LOT_ depends on the natue of the pages being served, Is the underlying data fairly 'static', or is it being frequently updated? If 'updated', you need to take into consideration things like 'how often', 'how large', and 'how localized' (in terms of the filesystem structure), are the updates. If file access is almost exclusively reads, the filesystem choice doesn't make much difference O/S 'caching', which occurs above the filesystem level, will handle the 'most frequently accessed' stuff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
--On August 16, 2012 6:02:57 PM +0100 Steve O'Hara-Smith st...@sohara.org wrote: On Thu, 16 Aug 2012 10:45:25 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? That's an average of about 3 hits per second. If it's static pages then pretty much anything will handle it easily (but please don't use FAT). If it's dynamic then the whole problem is more complex than a simple page rate. If that load is bursty it may make a difference too. Thanks for the reply. It's a combination. There are many static pages, but there is also a php-mysql forum that generates pages on the fly. It accounts for about half of the traffic. I've always used ufs but am wondering if switching to zfs would make sense. This stats page might answer some of your questions: http://www.stovebolt.com/stats/ Basically traffic is steady but it's busiest in the evenings (US time zones) Other considerations may come into play - how big is this filesystem (number of files, maximum number of entries in a directory, volume of data) ? Are there many users needing to be protected from each other ? What about archives ? snapshots ? growth ? churn ? uptime requirements, disaster recovery time ? I don't even know where to begin. There's about 15G of data on the server. Maybe this will help answer your questions: # sysctl -a | grep file kern.maxfiles: 12328 kern.bootfile: /boot/kernel/kernel kern.maxfilesperproc: 11095 kern.openfiles: 492 kern.corefile: %N.core kern.filedelay: 30 p1003_1b.mapped_files: 1 last pid: 40369; load averages: 0.01, 0.03, 0.00 up 104+09:33:44 13:14:49 137 processes: 1 running, 136 sleeping CPU: 0.7% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.2% idle Mem: 229M Active, 6108M Inact, 1056M Wired, 15M Cache, 828M Buf, 514M Free Swap: 16G Total, 28K Used, 16G Free The system is not being stressed. If by users, you means shell accounts, there's two, so that's not really an issue. The site has grown organically over the years from a few hundred hits a month to the now 6-8 million hits (depends on the time of year and the weather - mechanics are usually out in the garage if it's sunny and on the computer when it's not). Uptime is not an issue. The owners have repeatedly said if the site is down for two days they don't care. (The forum users don't feel that way though!) We've had one disaster (hard drive failure and raid failed while I was on vacation), and it took about 36 hours to get back online, but that was 10 years ago. The site doesn't go down - it's running on FreeBSD. :-) -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
Paul Schmehl writes: That's an average of about 3 hits per second. If it's static pages then pretty much anything will handle it easily (but please don't use FAT). If it's dynamic then the whole problem is more complex than a simple page rate. If that load is bursty it may make a difference too. Thanks for the reply. It's a combination. There are many static pages, but there is also a php-mysql forum that generates pages on the fly. It accounts for about half of the traffic. I've always used ufs but am wondering if switching to zfs would make sense. ZFS is known to use much more RAM than UFS. While (from the 'top' below) you have enough ... is that RAM best used for ZFS, or for something else? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
On Thu, 16 Aug 2012 13:16:26 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On August 16, 2012 6:02:57 PM +0100 Steve O'Hara-Smith st...@sohara.org wrote: On Thu, 16 Aug 2012 10:45:25 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? That's an average of about 3 hits per second. If it's static pages then pretty much anything will handle it easily (but please don't use FAT). If it's dynamic then the whole problem is more complex than a simple page rate. If that load is bursty it may make a difference too. Thanks for the reply. It's a combination. There are many static pages, but there is also a php-mysql forum that generates pages on the fly. It accounts for about half of the traffic. I've always used ufs but am wondering if switching to zfs would make sense. This stats page might answer some of your questions: http://www.stovebolt.com/stats/ Basically traffic is steady but it's busiest in the evenings (US time zones) Other considerations may come into play - how big is this filesystem (number of files, maximum number of entries in a directory, volume of data) ? Are there many users needing to be protected from each other ? What about archives ? snapshots ? growth ? churn ? uptime requirements, disaster recovery time ? I don't even know where to begin. There's about 15G of data on the server. OK I would say there's no pressing reason to consider ZFS for this purpose. You'd save a bit of time in crash recovery with no fsck going on, and perhaps the checksum mechanism would give some peace of mind - but really in 15GB silent corruption is a very slow process - now if it were 15TB ... last pid: 40369; load averages: 0.01, 0.03, 0.00 up 104+09:33:44 13:14:49 137 processes: 1 running, 136 sleeping CPU: 0.7% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.2% idle Mem: 229M Active, 6108M Inact, 1056M Wired, 15M Cache, 828M Buf, 514M Free Swap: 16G Total, 28K Used, 16G Free OTOH you have plenty of memory lying around doing nothing much (6108M inactive) so you can easily support ZFS if you want to play with it's features (the smooth integration of volume management and filesystem is rather cool). The system is not being stressed. If by users, you means shell accounts, there's two, so that's not really an issue. OK so no need for fancy quota schemes then. Uptime is not an issue. The owners have repeatedly said if the site is down for two days they don't care. (The forum users don't feel that way though!) We've had one disaster (hard drive failure and raid failed while I was on vacation), and it took about 36 hours to get back online, but that was 10 years ago. The site doesn't go down - it's running on FreeBSD. :-) It sounds like you have backups or at least some means of restoring the site in the event of disaster so that's all good. If there was a pressing need to be able to get back up fairly quickly and easily I'd be suggesting ZFS in RAID1 with a hot swap bay in which a third disc goes, attached as a third mirror, periodically split it off the mirror take it off site, and replace it with the one that's been off site. There's really nothing here that's pushing you in any particular direction for a filesystem, at 15GB if performance ever becomes a problem a RAID1 of SSDs with UFS would make it fly probably into the hundreds of hits per second range. -- Steve O'Hara-Smith | Directable Mirror Arrays C:WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
--On August 16, 2012 9:42:30 PM +0100 Steve O'Hara-Smith st...@sohara.org wrote: I don't even know where to begin. There's about 15G of data on the server. OK I would say there's no pressing reason to consider ZFS for this purpose. You'd save a bit of time in crash recovery with no fsck going on, and perhaps the checksum mechanism would give some peace of mind - but really in 15GB silent corruption is a very slow process - now if it were 15TB ... Thanks. last pid: 40369; load averages: 0.01, 0.03, 0.00 up 104+09:33:44 13:14:49 137 processes: 1 running, 136 sleeping CPU: 0.7% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.2% idle Mem: 229M Active, 6108M Inact, 1056M Wired, 15M Cache, 828M Buf, 514M Free Swap: 16G Total, 28K Used, 16G Free OTOH you have plenty of memory lying around doing nothing much (6108M inactive) so you can easily support ZFS if you want to play with it's features (the smooth integration of volume management and filesystem is rather cool). It's hard, nowadays, to buy a server that's too small for our needs. Most of them are way overspec'd for what this server does. Which is a nice luxury to have. It sounds like you have backups or at least some means of restoring the site in the event of disaster so that's all good. Yes, daily, and the servers are always configured in RAID1. If there was a pressing need to be able to get back up fairly quickly and easily I'd be suggesting ZFS in RAID1 with a hot swap bay in which a third disc goes, attached as a third mirror, periodically split it off the mirror take it off site, and replace it with the one that's been off site. There's really nothing here that's pushing you in any particular direction for a filesystem, at 15GB if performance ever becomes a problem a RAID1 of SSDs with UFS would make it fly probably into the hundreds of hits per second range. Thanks for the input, Steve. I appreciate it. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
On 08/16/2012 01:16 PM, Paul Schmehl wrote: Paul Schmehl pschmehl_li...@tx.rr.com wrote: Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? With only 15G of data, I'd recommend a pair of 60G SSD drives like the OCZ Vertex IIIs (About $1/G these days) wired into a *hardware* RAID controller setup to mirror them. This gives you blazing speed and reliability. If you want to add another drive, you can make it RAID 5 which - with the right cabinet and mounting hardware - would give you hotswap capability. I know people are fond of software RAID but I personally do not consider this a very high reliability technology unless you're running true datacenter class hardware with redundant everything (disk, NIC, fiber ...) and that's probably overkill in this case. Good RAID controllers are available from a number of manufacturers. I dunno if FreeBSD supports them, but Rocket has a good reputation (though I've never used them) as do both Adaptec and LSI. In any case, a controller plus 3 drives would probably only set you back in the $500-ish area which seems like a reasonable price point. Furthermore, depending on the amount of stuff that you're serving that is static vs. dynamic, you may get benefit from increasing memory (thereby increasing the likelihood of a cache hit) and increasing the minimum/threshold values for the number of httpd processing running all the time. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
OK I would say there's no pressing reason to consider ZFS for this another ZFS fanatics. it is about performance. direction for a filesystem, at 15GB if performance ever becomes a problem a RAID1 of SSDs with UFS would make it fly probably into the hundreds of hits per second range. classic for ZFS and modern things fanatics. lots of talk about high end hardware nothing about a thread. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
the OCZ Vertex IIIs (About $1/G these days) wired into a *hardware* RAID controller setup to mirror them. This gives you blazing speed just like i would read some popular street PC newspaper. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Best file system for a busy webserver
On Thu, Aug 16, 2012 at 10:45 AM, Paul Schmehl pschmehl_li...@tx.rr.comwrote: Does anyone have any opinions on which file system is best for a busy webserver (7 million hits/month)? Is anyone one system noticeably better than any other? Just curious. I'm getting ready to setup a new box running FreeBSD 9, and since I'm starting from scratch, I'm questioning all my previous assumptions. Sounds like you have ample hardware, so I would probably consider ZFS. You get a lot of other options with it which simply aren't available or harder to manage on a UFS system. Things like data integrity, ZIL/ARC, live low-cost snapshots, diff'ing the snapshot, transparent compression, etc all come with ZFS. Great tools for certain scenarios. Properly setup, ZFS RAID functionality will own any hardware raid solution ever presented because ZFS doesn't rely on a battery for consistency, nor do they provide most other features stated including integrity oriented ones. ZFS is intended to work with raw disk/JBOD. Good controllers are still important, they simply don't have the knowledge to use them at peak efficiency. I don't see much benefit to SSD's for this use case. All the common files should be in the fs cache which is at least an order of magnitude faster than flash based memory, and finding enterprise SSD's(preferably SLC) which obey FLUSH commands appropriately and have a capicitor appropriate to production use is something more of a crapshoot than traditional SATA/SAS drives. All that being said, UFS is fine too. I use it most often for light VM installs and where resources are scarce. However the 2 single biggest ZFS feature I like are the data integrity and transparent compression are wonderful which aren't available in UFS. ZFS snapshots are much more functional as well and go well w/ zfs send/receive. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can't write to NTFS file system
Hi List. I'm using fusefs_enable=YES in /etc/rc.conf And /dev/ad4s2 /home/mnt/windows ntfs rw,noauto 0 0 in /etc/fstab I can read the NTFS file system and copy from it but I can't copy to it. When I try copying I get No such file or directory Is that default behaviour? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't write to NTFS file system
On 08/09/2012 13:37, Leslie Jensen wrote: Hi List. I'm using fusefs_enable=YES in /etc/rc.conf And /dev/ad4s2 /home/mnt/windows ntfs rw,noauto 0 0 in /etc/fstab I can read the NTFS file system and copy from it but I can't copy to it. When I try copying I get No such file or directory Is that default behaviour? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I think your /etc/fstabrecord should rather be: /dev/ad4s2 /home/mnt/windows ntfs-3g rw 0 0 The ntfs is not from the FUSE project, it's native and read-only. And the noauto is for keeping the file system from being mounted automatically at boot. -Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
alternatively - use tar. What I was trying to achieve, which I haven't done yet, was a smallish dump of the core system. By that I mean system + ports, without distfiles, etc. Then a separate dump of user data, which is considerably larger. At this point I am thinking I should do this: make clean distclean ports to remove temporary stuff set /usr/home NODUMP dump /, /var, and /usr unset /usr/home NODUMP dump /usr/home really - use tar. dump is not for that, but to QUICKLY dump a filesystem. on SSD - both are faster than writing to backup target disk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? i really have no idea why you just don't dump it all? restore have -i option that allow you to partially restore files from a dump. I have SSD, single partition and i use dump to backup it to external hard disk. alternatively - use tar. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
On 06/16/12 10:19, Wojciech Puchar wrote: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? i really have no idea why you just don't dump it all? restore have -i option that allow you to partially restore files from a dump. I have SSD, single partition and i use dump to backup it to external hard disk. alternatively - use tar. What I was trying to achieve, which I haven't done yet, was a smallish dump of the core system. By that I mean system + ports, without distfiles, etc. Then a separate dump of user data, which is considerably larger. At this point I am thinking I should do this: make clean distclean ports to remove temporary stuff set /usr/home NODUMP dump /, /var, and /usr unset /usr/home NODUMP dump /usr/home ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
dumping file system subtree (/var)
When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
Would rsync or cpdup from single user mode cover your needs? Should cover everything and then you can just reboot into your newly partitioned system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
2012-06-07 22:05, Gary Aitken skrev: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
On Thu, 7 Jun 2012, Gary Aitken wrote: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. There are several things in /var that are worth keeping, and they are pretty small. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? Snapshots don't have to be made separately, dump's -L option does that automatically: http://www.wonkity.com/~wblock/docs/html/backup.html Restoring from a dumpfile is an easy way. net/rsync has a config option to support flags, but I haven't tried it. And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? When I did that recently, I put /var on a small separate partition but used tmpfs(5) for /tmp. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Wed, Apr 18, 2012 at 02:12:41PM +0200, Julian H. Stacey wrote: Hi Julian, Hi, Reference: From:Xavier xavierfreebsdquesti...@gmail.com Date:Sat, 7 Apr 2012 22:25:28 +0200 Message-id:CALe6D=vpy0rk1=- 9rvtv46xp8zd4xvzngb1cbwwacdazwtq...@mail.gmail.com Xavier wrote: On Sat, Apr 07, 2012 at 04:15:41PM -0400, ill...@gmail.com wrote: Hi, On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ perhaps? Note---^^ If that still doesn't work, try adding -r in there (as ext2fs might not support r/w in your configuration). casa# mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# casa# mount -r -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# You have more ideas ? With 9.0-RELEASE generic kernel: man mount ... man 2 nmount The type argument names the file system. The types of file systems known to the system can be obtained with lsvfs(1). lsvfs FilesystemRefs Flags - --- devfs1 synthetic msdosfs 0 nfs 0 network procfs 0 synthetic cd9660 0 read-only ufs 1 cd /boot/kernel ; find . -name \*ext\* -print kldload /boot/kernel/ext2fs.ko ; lsvfs # Adds ext2fs 0 man ext2fs To link into the kernel: options EXT2FS To load as a kernel loadable module: kldload ext2fs No mention of ext3 there, nor from find (above). .. so you May be out of luck .. Divide the problem. Reduce simulltaneous testing of backslash ext3. Delete all backslash junk during test. Try su ; mkdir /mnt/test ; mount -r -t ext2fs /dev/da1a /mnt/test I try: casa# kldstat | grep ext 101 0xc93b9000 1ext2fs.ko casa% lsvfs | grep ext ext2fs 0 casa# disktype /dev/da0 --- /dev/da0 Character device, size 14.92 GiB (16025387008 bytes) DOS/MBR partition map Partition 1: 13.93 GiB (14961082368 bytes, 29220864 sectors from 2048, bootable) Type 0x83 (Linux) Ext3 file system UUID DF70360E-9DD3-436D-9627-A614FB0FD24E (DCE, v4) Last mounted at / Volume size 13.93 GiB (14961082368 bytes, 3652608 blocks of 4 KiB) Partition 2: 0.988 GiB (1061159936 bytes, 2072578 sectors from 29224958) Type 0x05 (Extended) Partition 5: 1012 MiB (1061158912 bytes, 2072576 sectors from 29224958+2) Type 0x82 (Linux swap / Solaris) casa% ls /dev/da0* /dev/da0/dev/da0s1 /dev/da0s2 /dev/da0s5 How can get the correct da0 node for your mount(8) command ? Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
Hi,
Reference:
From: Xavier xavierfreebsdquesti...@gmail.com
Date: Sat, 7 Apr 2012 22:25:28 +0200
Message-id:
CALe6D=vpy0rk1=-9rvtv46xp8zd4xvzngb1cbwwacdazwtq...@mail.gmail.com
Xavier wrote:
On Sat, Apr 07, 2012 at 04:15:41PM -0400, ill...@gmail.com wrote:
Hi,
On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote:
Hi to all,
I have:
casa# disktype /dev/da1
--- /dev/da1
Character device, size 3.771 GiB (4048551936 bytes)
FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2)
BSD disklabel (at sector 1), 8 partitions
Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0)
Type 0 (Unused)
DOS/MBR partition map
Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63)
Type 0x83 (Linux)
Ext3 file system
UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4)
Last mounted at /
Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB)
Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095)
Type 0x05 (Extended)
Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63)
Type 0x82 (Linux swap / Solaris)
Linux swap, version 2, subversion 1, 4 KiB pages, little-endian
Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB)
I'm running from FreeBSD 9.0-RELEASE
I try:
casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/
mount: /dev/da1a : Invalid argument
How can I mount it ?
mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/
perhaps? Note---^^
If that still doesn't work, try adding -r in there (as ext2fs might not
support r/w in your configuration).
casa# mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/
mount: /dev/da1s1 : No such file or directory
casa#
casa# mount -r -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/
mount: /dev/da1s1 : No such file or directory
casa#
You have more ideas ?
With 9.0-RELEASE generic kernel:
man mount
...
man 2 nmount
The type argument names the file system. The types of file
systems known to the system can be obtained with lsvfs(1).
lsvfs
FilesystemRefs Flags
- ---
devfs1 synthetic
msdosfs 0
nfs 0 network
procfs 0 synthetic
cd9660 0 read-only
ufs 1
cd /boot/kernel ; find . -name \*ext\* -print
kldload /boot/kernel/ext2fs.ko ; lsvfs
# Adds
ext2fs 0
man ext2fs
To link into the kernel:
options EXT2FS
To load as a kernel loadable module:
kldload ext2fs
No mention of ext3 there, nor from find (above).
.. so you May be out of luck ..
Divide the problem. Reduce simulltaneous testing of backslash ext3.
Delete all backslash junk during test. Try
su ; mkdir /mnt/test ; mount -r -t ext2fs /dev/da1a /mnt/test
If that likely too fails, then select a list:
freebsd...@freebsd.org
or
freebsd-curr...@freebsd.org
+ cc code authors on freebsd
{ see names in base of man ext2fs` look in sources or cvs maybe }
Ask them if anyone is known to be working on Ext3 on FreeBSD
(or *OtherBSD, as that'd be a good start for a port)
If all that fails, insert stick in a Linux box (*),
copy data from the ext3 stick, reformat stick as Ext2, write the data back.
Ext2 doesnt need the latest FreeBSD-9, at least FreeBSD-8.2
can also handle Ext2.
Linux boxes can be found in unexpected places, eg some
media devices are built on Linux, (Some some manufacturers are not
aware BSD offers more liberal licensing than FSF). Whether
such devices can reformat to user selected format I haven't yet had
access to try so you might need a real Linux PC to re-format.
Examples of media boxes:
Iomega ScreenPlay TV Link, Director Edition
high definition multimedia player
http://go.iomega.com/section?p=4760secid=42740#tech_specsItem_tab
External USB Drive Format:
NTFS (default), FAT32, Mac OS Extended (HFS+)**, Ext2 or Ext3.
(No mention of UFS, so presumably a Linux, I will collect one soon).
http://www.humaxfoxsathdr.co.uk/
Foxsat-HDR/500
http://www.humaxdirect.co.uk/product.asp?ProdRef=10087#more-info
(Not stated what this supports.)
Dreambox 800
http://www.dreambox800.co.uk/Dreambox-800-Satellite-Receiver-pro
(Not stated what this supports, but based on Linux)
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like a play script, indent with .
Format: Plain text
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Wed, 18 Apr 2012 14:12:41 +0200 Julian H. Stacey wrote: No mention of ext3 there, nor from find (above). .. so you May be out of luck .. ext3 is ext2+journalling. If fsck supports ext3, then it can sync the journal and the partition can be safely mounted as ext2. It's a long time since I've used ext3 so this may have changed, but when I did it needed an fsck from ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
Hi, Reference: From: RW rwmailli...@googlemail.com Date: Wed, 18 Apr 2012 14:13:19 +0100 Message-id: 20120418141319.7cb8c...@gumby.homeunix.com RW wrote: On Wed, 18 Apr 2012 14:12:41 +0200 Julian H. Stacey wrote: No mention of ext3 there, nor from find (above). .. so you May be out of luck .. ext3 is ext2+journalling. If fsck supports ext3, then it can sync the journal and the partition can be safely mounted as ext2. It's a long time since I've used ext3 so this may have changed, but when I did it needed an fsck from ports. I tried to find that for original poster Xavier (cc restored in case Xavier not on questions@), using cd /pub/FreeBSD/branches/-current/ports echo `find . -type f | xargs grep -i -l fsck` | xargs grep -i -l ext3 got: ./emulators/linux_base-c6/pkg-plist ./emulators/linux_base-f10/pkg-plist ./emulators/linux_base-fc4/pkg-plist ./emulators/linux_dist-gentoo-stage3/pkg-plist.i486 ./emulators/linux_dist-gentoo-stage3/pkg-plist.i686 ./sysutils/e2fsprogs/Makefile COMMENT?= Utilities library to manipulate ext2/3/4 filesystems Xavier, I suggest try /usr/ports/sysutils/e2fsprogs I saw this warning building on 8.2-RELEASE: If you format ext2 file systems with other operating systems, make sure that mke2fs is called with -I 128 for partitions that you plan to share with FreeBSD. (Not tried building it on 9 as I'm rebuilding machine now.) /usr/local/share/doc/e2fsprogs/ COPYING http://e2fsprogs.sourceforge.net Says there it supports ext3 4 too. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
from Xavier xavierfreebsdquesti...@gmail.com: I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? I'm confused between the BSD disklabel and DOS/MBR partition map. What does (running from Linux) fdisk -lu /dev/sdb (or whatever the Linux name for that disk is) show? How do you mount that Linux ext3fs partition in Linux? That knowledge might help me figure how to mount that partition from FreeBSD. I'm still not sure how or if FreeBSD supports ext3fs as opposed to ext2fs. I don't see the rationale for setting up an extended partition when you only use two partitions. The second (Linux swap) partition could be primary, and you would be well under the quota of four primary partitions. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sun, Apr 08, 2012 at 06:32:36AM -0400, Thomas Mueller wrote: Hi Thomas, from Xavier xavierfreebsdquesti...@gmail.com: I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? I'm confused between the BSD disklabel and DOS/MBR partition map. What does (running from Linux) fdisk -lu /dev/sdb (or whatever the Linux name for that disk is) show? ^^ I'll run that command line from a GNU/Linux ( not from FreeBSD ) ? How do you mount that Linux ext3fs partition in Linux? That knowledge might help me figure how to mount that partition from FreeBSD. I don't probe it. /dev/da1 is a USB pen drive with GNU/Linux OS. Well, I wait to confirm that command ... Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 10:06:44PM +0300, Odhiambo Washington wrote: Hi Odhiambo, man mount mount fstype device mount-point Yes, but look: I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument I don't know why !? Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ perhaps? Note---^^ If that still doesn't work, try adding -r in there (as ext2fs might not support r/w in your configuration). -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 04:15:41PM -0400, ill...@gmail.com wrote: Hi, On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ perhaps? Note---^^ If that still doesn't work, try adding -r in there (as ext2fs might not support r/w in your configuration). casa# mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# casa# mount -r -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# You have more ideas ? Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
I don't know why !? Is ext2fs.ko loaded? Does /var/log/messages reveal anything? Yes : casa# kldstat | grep ext 91 0xc8806000 1ext2fs.ko casa# I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument /var/log/messages : Apr 7 22:16:35 casa kernel: ext2fs: da1a: wrong magic number 0 (expected 0xef53 What is the output from gpart list? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 06:25:29PM -0500, Adam Vande More wrote: Hi Adam, I don't know why !? Is ext2fs.ko loaded? Does /var/log/messages reveal anything? Yes : casa# kldstat | grep ext 91 0xc8806000 1ext2fs.ko casa# I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument /var/log/messages : Apr 7 22:16:35 casa kernel: ext2fs: da1a: wrong magic number 0 (expected 0xef53 What is the output from gpart list? ###cut here### Geom name: da1 modified: false state: OK fwheads: 255 fwsectors: 63 last: 7907327 first: 0 entries: 8 scheme: BSD Providers: 1. Name: da1a Mediasize: 2302703616 (2.1G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 8192 Mode: r0w0e0 rawtype: 0 length: 2302703616 offset: 8192 type: !0 index: 1 end: 4497483 start: 16 Consumers: 1. Name: da1 Mediasize: 4048551936 (3.8G) Sectorsize: 512 Mode: r0w0e0 ###cut here### Have ideas ? Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: microSD ext3 file system
Hello, I have some trouble with a microSD card (or with the controler) in my Linux based cellphone (Openmoko Freerunner). One of the hints I got is to check the microSD card with a Linux tool badblocks(8) http://linux.die.net/man/8/badblocks As I do not have Linux boxes at home, I looked into our ports with no luck for badblocks... Is there some equivalent in FreeBSD which I could use to check /dev/da0 (as this the microSD is presented in my laptop) for bad 'sectors'? FWIW, I've found as well this very interesting article: https://lwn.net/Articles/428584/ which says for example: «... In contrast, the more common SD cards and USB flash drives are very sensitive to specific access patterns and can show very high latencies for writes unless they are used with the preformatted FAT32 file layout. As an example, a desktop machine using a 16 GB, 25 MB/s CompactFlash card to hold an ext3 root filesystem ended up freezing the user interface for minutes during phases of intensive block I/O, despite having gigabytes of free RAM available. Similar problems often happen on small embedded and mobile machines that rely on SD cards for their file systems. ...» Thanks matthias - Forwarded message from Matthias Apitz g...@unixarea.de - Date: Mon, 2 Apr 2012 19:52:40 +0200 From: Matthias Apitz g...@unixarea.de To: commun...@lists.openmoko.org Subject: microSD ext3 file system Hello, After some hours of testing I'm now totally lost with creating an ext3 file system on a (new) 4GB micro SD card. Using my FR (running SHR) I created one new partition on the SD with fdisk(1) and it looks like this: root@om-gta02 ~ # fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 3953 MB, 3953131520 bytes 4 heads, 16 sectors/track, 120640 cylinders Units = cylinders of 64 * 512 = 32768 bytes Sector size (logical/physical): 512 bytes / 512 bytes Disk identifier: 0x0aecb0ac Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 120640 3860472 83 Linux Then I created the ext3 file system on it with: root@om-gta02 ~ # mkfs.ext3 /dev/mmcblk0p1 mke2fs 1.41.9 (22-Aug-2009) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 241440 inodes, 965118 blocks 48255 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=989855744 30 block groups 32768 blocks per group, 32768 fragments per group 8048 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 32 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. now mounting against the /etc/fstab line failes: root@om-gta02 ~ # mount /media/card mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mounting with -t ext3 works and after this as well mounting with the normal line in fstab(5) works too: root@om-gta02 ~ # mount -t ext3 /dev/mmcblk0p1 /media/card root@om-gta02 ~ # umount /media/card root@om-gta02 ~ # mount /media/card root@om-gta02 ~ # and it is really mounted: root@om-gta02 ~ # mount ... /dev/mmcblk0p1 on /media/card type ext3 (rw,errors=continue,data=ordered) now I create a dir and copy over some files from the host connected via USB: root@om-gta02 ~ # mkdir /media/card/dic host: $ scp -rp stardict-duden-2.4.2 root@miko:/media/card/dic duden.ifo 100% 155 0.2KB/s 00:00 duden.idx 100% 2360KB 786.7KB/s 00:03 duden.dict.dz 100% 6719KB 559.9KB/s 00:12 scp: /media/card/dic/stardict-duden-2.4.2/duden.dict.dz: Read-only file system scp: /media/card/dic/stardict-duden-2.4.2/duden.idx.oft: Read-only file system scp: /media/card/dic/stardict-duden-2.4.2/duden(2).idx.oft: Read-only file system the SCP fails and magically now the SD in the FR is mounted read-only: root@om-gta02 ~ # mount ... /dev/mmcblk0p1 on /media/card type ext3 (ro,errors=continue,data=ordered) What is wrong or what do I wrong with this SD card? Thanks matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ Openmoko community mailing list commun...@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community - End forwarded message - -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11
Re: microSD ext3 file system
On Wed, Apr 4, 2012 at 12:25 AM, Matthias Apitz g...@unixarea.de wrote: I have some trouble with a microSD card (or with the controler) in my Linux based cellphone (Openmoko Freerunner). One of the hints I got is to check the microSD card with a Linux tool badblocks(8) http://linux.die.net/man/8/badblocks Not exactly what you are asking for but something like this: recoverdisk /dev/da0 /dev/da0 -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: find not traversing all directories on a single zfs file system
On 28/02/2012 02:21, Robert Banfield wrote: I have some additional information that I didnt see before actually digging into the log file. It is quite interesting. There are 82,206 subdirectories in one of the folders. Like this: /zfs_mount/directoryA/token[1-82206]/various_tileset_files When looking at the output of find, here is what I see: Lines 1-9996943: The output of find, good as good can be Lines 9996944-10062479: Subdirectory entries only, it traversed none of them. Notice 10062479-9996944+1 = 65536 = 2^16 So, of the 82206 subdirectories, the first 82206-2^16 were traversed, and the final 2^16 were not. The plot thickens... Now this is very interesting indeed. 80,000 subdirectories is quite a lot.. As is a grand total of more than 10,000,000 files. Hmmm... and you see the find problem just when searching within the structure under directoryA? I think you have found a bug, although whether it is in find(1), the filesystem or elsewhere is not clear. Given that 'ls -R' shows the same problem, the bug could be in fts(3). Still, that's a testable hypothesis. Let me see if I can reproduce the problem. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
find not traversing all directories on a single zfs file system
Summary: I am executing the command find . ../file_list and it is not traversing all the subdirectories it encounters along the way. There is no separate file system mounted along the path. Long version: I'm new to FreeBSD and ZFS (many years of linux experience though), so my apologies if I'm missing something straightforward here. This is a tile server which has tens of millions of mostly small files. I'm logged in as root, and there is no networked file system anywhere in the mix. I'm using the version of find installed with FreeBSD 9.0-RELEASE amd64. cd /zfs_mount_point/mydir find . ../file_list I would presume that file_list contains a list of every file and directory inside of /zfs_mount_point/mydir, however some directories contain only the directory entry without any of the file and subdirectories it contains. As an example, file_list contains: ./dataset_tiles ./dataset_tiles/token1 ./dataset_tiles/token1/kml ./dataset_tiles/token1/kml/kml.png ./dataset_tiles/token2 ./dataset_tiles/token3 ./dataset_tiles/token3/kml ... The problem is ./dataset_tiles/token2 is a directory, and none of its entries appear anywhere in the file_list. Yet if I do the following: find ./dataset_tiles/token2 I get a list of everything that I would expect to have been in file_list, but did not. ls -l shows the entry type character as 'd'. token2 is just a subdirectory of dataset_tiles, not a separate mount point. I should have all the requisite permissions to access the files in that directory, and I can run find successfully if I specify any of the directories which do not seem to be working. Here's an actual 'ls -ld' on one of the directories not working: ls -ld 967c4f32-8a9e-0459-8e94-c911e41be43b/ drwxr-xr-x 10 root wheel 10 Feb 4 21:45 967c4f32-8a9e-0459-8e94-c911e41be43b/ The only other tidbit of information I can think to add is I also tried running find -d . with no overall change in output other than the order the directories were searched. Any idea what's going on? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: find not traversing all directories on a single zfs file system
On 27/02/2012 21:52, Robert Banfield wrote: Long version: I'm new to FreeBSD and ZFS (many years of linux experience though), so my apologies if I'm missing something straightforward here. This is a tile server which has tens of millions of mostly small files. I'm logged in as root, and there is no networked file system anywhere in the mix. I'm using the version of find installed with FreeBSD 9.0-RELEASE amd64. cd /zfs_mount_point/mydir find . ../file_list I would presume that file_list contains a list of every file and directory inside of /zfs_mount_point/mydir, however some directories contain only the directory entry without any of the file and subdirectories it contains. These are all actual directories -- no symbolic link or anything like that? I assume permissions are not the problem? All directories have at least mode r_x for your user id? (Hmmm... but you are logged in as root -- can't be that then.) How about ACLs? Are you using those at all on your filesystem? The symptoms you are observing are definitely incorrect, and not at all what the vast majority of find(1) users would experience. Something is definitely a bit fubar on your machine. It would be useful to try and establish if it is the find(1) program giving bogus results, or whether it is some other part of the system. Do other methods of printing out the filesystem contents suffer from the same problem -- eg. 'ls -R .' or 'tar -cvf /dev/null .' Is there anything in the system log or printed on the console? (Note: I always find it useful to enable the console.log and all.log by uncommenting the relevant lines in /etc/syslog.conf and following the other instructions there.) Also, is this 9.0-RELEASE straight from the installation media, or did you compile it yourself? If you compiled it yourself, what compiler did you use (gcc or clang)? What optimization and what architecture settings -- trying to tweak such things for maximum optimization frequently leads to dissapointment. If you installed onto ZFS, what procedure did you follow, given that bsdinstall doesn't have that capability yet? Was it by following one of the well-known recipes like http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot ? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: find not traversing all directories on a single zfs file system
On 02/27/2012 05:53 PM, Matthew Seaman wrote: These are all actual directories -- no symbolic link or anything like that? I assume permissions are not the problem? All directories have at least mode r_x for your user id? (Hmmm... but you are logged in as root -- can't be that then.) How about ACLs? Are you using those at all on your filesystem? There are no symbolic links, nor any ACLs at all anywhere on the system. All the directories have rwx for root, and permissions are not a problem. The symptoms you are observing are definitely incorrect, and not at all what the vast majority of find(1) users would experience. Something is definitely a bit fubar on your machine. It would be useful to try and establish if it is the find(1) program giving bogus results, or whether it is some other part of the system. Do other methods of printing out the filesystem contents suffer from the same problem -- eg. 'ls -R .' or 'tar -cvf /dev/null .' ls -R appears to be traversing all subdirectories. Is there anything in the system log or printed on the console? (Note: I always find it useful to enable the console.log and all.log by uncommenting the relevant lines in /etc/syslog.conf and following the other instructions there.) da0 runs the operating system. da1-12 are set up as a RAIDZ2 with 2 hot spares. # zpool status pool: tank0 state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM tank0ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 label/zfsdisk1 ONLINE 0 0 0 label/zfsdisk2 ONLINE 0 0 0 label/zfsdisk3 ONLINE 0 0 0 label/zfsdisk4 ONLINE 0 0 0 label/zfsdisk5 ONLINE 0 0 0 label/zfsdisk6 ONLINE 0 0 0 label/zfsdisk7 ONLINE 0 0 0 label/zfsdisk8 ONLINE 0 0 0 label/zfsdisk9 ONLINE 0 0 0 label/zfsdisk10 ONLINE 0 0 0 spares label/zfsdisk11AVAIL label/zfsdisk12AVAIL # glabel status Name Status Components gptid/d49367f4-5cfc-11e1-be4b-000423b4b110 N/A da0p1 label/zfsdisk1 N/A da1 label/zfsdisk2 N/A da2 label/zfsdisk3 N/A da3 label/zfsdisk4 N/A da4 label/zfsdisk5 N/A da5 label/zfsdisk6 N/A da6 label/zfsdisk7 N/A da7 label/zfsdisk8 N/A da8 label/zfsdisk9 N/A da9 label/zfsdisk10 N/A da10 label/zfsdisk11 N/A da11 label/zfsdisk12 N/A da12 These messages appear in the output of dmesg: GEOM: da1: the primary GPT table is corrupt or invalid. GEOM: da1: using the secondary instead -- recovery strongly advised. (repeat for da2 - da12) GEOM: da1: corrupt or invalid GPT detected. GEOM: da1: GPT rejected -- may not be recoverable. GEOM: da1: corrupt or invalid GPT detected. GEOM: da1: GPT rejected -- may not be recoverable. (repeat for da2-da12) GEOM: label/zfsdisk1: corrupt or invalid GPT detected. GEOM: label/zfsdisk1: GPT rejected -- may not be recoverable. Could this be related, or a separate issue? Also, is this 9.0-RELEASE straight from the installation media, or did you compile it yourself? If you compiled it yourself, what compiler did you use (gcc or clang)? What optimization and what architecture settings -- trying to tweak such things for maximum optimization frequently leads to dissapointment. This is straight from the 64-bit memstick install. I have used both the standard install /usr/bin/find as well as a compiled /usr/src/usr.bin/find/ and both give the same results. I have no tweaks for zfs other than to zfs_enable on boot. Because this machine has 16GB of RAM, I believe prefetch is automatically enabled. I have some additional information that I didnt see before actually digging into the log file. It is quite interesting. There are 82,206 subdirectories in one of the folders. Like this: /zfs_mount/directoryA/token[1-82206]/various_tileset_files When looking at the output of find, here is what I see: Lines 1-9996943: The output of find, good as good can be Lines 9996944-10062479: Subdirectory entries only, it traversed none of them. Notice 10062479-9996944+1 = 65536 = 2^16 So, of the 82206 subdirectories, the first 82206-2^16 were traversed, and the final 2^16 were not. The plot thickens... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
Re: find not traversing all directories on a single zfs file system
On 02/27/2012 09:21 PM, Robert Banfield wrote: ls -R appears to be traversing all subdirectories. Scratch that... ls -R fails to traverse the same directories that find does. Is there a subdirectory limit in ZFS? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. The one directory I really want to put on a separate partition is /home . That way, you can fully rebuild/redo your system and keep user data. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On 2011/11/20 at 19:25, Thomas Mueller mueller6...@bellsouth.net wrote: from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. The one directory I really want to put on a separate partition is /home . That way, you can fully rebuild/redo your system and keep user data. Yes. I always put /home on a separate partition. Actually, my /home is on a ZFS partition which is of more scalability and easier snapshots. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. I always size /var to 2G or 3G, which is typical for me. I seldom run freebsd-update, but upgrade from sources instead. I only encountered problems with Xorg that crashed filling up /var with core dumps... I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . It is long before I started thinking of joining /usr and /usr/local into one partition. However, my current installation dates back to FreeBSD 6 or 7. Many things changed exept the filesystem layout. I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. I guess 'portsnap fetch update' is run only after the ports tree is there. For a fresh install of the ports tree, 'portsnap fetch extract' is the correct way. For me, I only pull the ports tree with 'portsnap'. That way, I can complete a fresh install of FreeBSD in less than 20 minutes. Tom -- If you've got them by the balls, their hearts and minds will follow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On Sun, Nov 20, 2011 at 11:25:35AM +, Thomas Mueller wrote: from darc...@gmail.com (Denise H. G.): I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. I don't like to put /var on a separate partition because of the danger of running short of space. I had nervous moments when running freebsd-update on the older computer and seeing the used part of /var grow. For that very reason, I put /var on a separate partition. Stuff being written to /var is most likely to over run stuff and trash a / partition. jerry I don't really see a need to put /usr/local on a separate partition, though conceivably you could build applications with both FreeBSD ports and NetBSD pkgsrc, but keep these separate. NetBSD pkgsrc has been ported to other (quasi-)Unixes including FreeBSD. Default directory corresponding to FreeBSD's /usr/local is /usr/pkg . I think I like FreeBSD ports better than NetBSD pkgsrc, the latter which I used only with NetBSD. I originally installed FreeBSD 9.0-BETA1 using bsdinstall on the USB stick, including the ports. There was a conflict when I ran portsnap fetch update, that didn't work. I had to run portsnap fetch and portsnap extract, scrapping the ports tree from bsdinstall in favor of the fresh ports tree. So now I know best to not install ports tree from bsdinstall; this would presumably apply for sysinstall too. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
file system on 9.0
Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Thanks in advance. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thanks in advance. Mitja http://jpgmag.com/people/lumiwa -- If you've got them by the balls, their hearts and minds will follow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On Sat, 19 Nov 2011 20:29:40 +0800 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. UFS_GJOURNAL is for gjournal not soft-update journalling. A file system doesn't actually need to be created with either soft-updates or soft-update journalling- it's something that can be turned of and on. And yes enabling it in the installer should be sufficient. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. There's no point in installing the default tree since portsnap has to do an initial extract. In general I'd suggest starting portsnap on an empty ports directory just to eliminate any minor cruft. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On Saturday 19 November 2011 06:29:40 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thank you and one more, please... Partitioning: if I choose guided than I got: freebsd-boot freebsd-ufs / freebsd-swap If I press enter on freebsd-ufs / than I got options to make moe partitions. Is it okay that I make /, /var, /tmp and /usr as I have now. Thank you very much for the help. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On 2011/11/19 at 21:18, RW rwmailli...@googlemail.com wrote: On Sat, 19 Nov 2011 20:29:40 +0800 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. UFS_GJOURNAL is for gjournal not soft-update journalling. A file system doesn't actually need to be created with either soft-updates or soft-update journalling- it's something that can be turned of and on. And yes enabling it in the installer should be sufficient. Thanks for clarifying. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. There's no point in installing the default tree since portsnap has to do an initial extract. In general I'd suggest starting portsnap on an empty ports directory just to eliminate any minor cruft. Yes. the ports tree on the installation CD/DVD is always old and only takes longer time to install than without them. -- If you've got them by the balls, their hearts and minds will follow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: file system on 9.0
On 2011/11/19 at 23:03, ajtiM lum...@gmail.com wrote: On Saturday 19 November 2011 06:29:40 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thank you and one more, please... Partitioning: if I choose guided than I got: freebsd-boot freebsd-ufs / freebsd-swap If I press enter on freebsd-ufs / than I got options to make moe partitions. Is it okay that I make /, /var, /tmp and /usr as I have now. I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. Thank you very much for the help. Mitja Regards. -- If you've got them by the balls, their hearts and minds will follow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Shouldn't GNU tar be ignoring /proc with --one-file-system?
I use Amanda to make nightly backups of a bunch of servers using GNU tar. However, gtar doesn't seem to respect its --one-file-system flag with /proc. Amanda runs a variation of this command: # /usr/local/bin/gtar --create --file - --directory / --one-file-system --sparse --ignore-failed-read --totals . /dev/null /usr/local/bin/gtar: ./proc: file changed as we read it Before I file a bug report, can anyone think of a legitimate reason why gtar would be touching /proc at all? Kirk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On Fri, November 18, 2011 10:34 am, Kirk Strauser wrote: I use Amanda to make nightly backups of a bunch of servers using GNU tar. However, gtar doesn't seem to respect its --one-file-system flag with /proc. Amanda runs a variation of this command: # /usr/local/bin/gtar --create --file - --directory / --one-file-system --sparse --ignore-failed-read --totals . /dev/null /usr/local/bin/gtar: ./proc: file changed as we read it Before I file a bug report, can anyone think of a legitimate reason why gtar would be touching /proc at all? Just a guess, really but: /proc is a file on /. /proc/* are files on /proc. The former is still on the root filesystem (if only as a directory stub to be used as a mountpoint), so reading it isn't leaving that filesystem. Reading anything *in* it would be. Just a thought. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On Fri, Nov 18, 2011 at 8:59 AM, Daniel Staal dst...@usa.net wrote: /proc is a file on /. /proc/* are files on /proc. The former is still on the root filesystem (if only as a directory stub to be used as a mountpoint), so reading it isn't leaving that filesystem. Reading anything *in* it would be. Just a thought. And a good one. Yes, that's it. It isn't crossing the mount point, but the mount point is part of the root filesystem. If you really want it to ignore the mount point itself, set the nodump flag and tell gtar to honor it: chflags nodump /proc gtar your options --nodump ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
From owner-freebsd-questi...@freebsd.org Fri Nov 18 09:36:09 2011 From: Kirk Strauser k...@strauser.com Date: Fri, 18 Nov 2011 09:34:18 -0600 To: FreeBSD Questions ML freebsd-questions@freebsd.org Subject: Shouldn't GNU tar be ignoring /proc with --one-file-system? I use Amanda to make nightly backups of a bunch of servers using GNU tar. Howe ver, gtar doesn't seem to respect its --one-file-system flag with /proc. Amand a runs a variation of this command: Don't blame the software. It is just doing *exactly* what you told it to. :) # /usr/local/bin/gtar --create --file - --directory / --one-file-system --sparse --ignore-failed-read --totals . /dev/null /usr/local/bin/gtar: ./proc: file changed as we read it Before I file a bug report, can anyone think of a legitimate reason why gtar would be touching /proc at all? Yup. You (or more properly, Amanda) _told_ it to. See the output of 'mount(8)' for the names of all the mounted filesystems on your machine. *NOTE*WELL* that '/proc' is *not* a separate filesystem. It is merely a _directory_ with a bunch of 'special' files in it. The 'error message' is accurate -- but it is _just_ a 'warning', and -- in *this* circumstance -- _totally_ innocuous. If you want to suppress generation of that error, simply add an '--exclude' for /proc to the Amanda run. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On 18/11/2011 17:18, Michael Sierchio wrote: On Fri, Nov 18, 2011 at 8:59 AM, Daniel Staal dst...@usa.net wrote: /proc is a file on /. /proc/* are files on /proc. The former is still on the root filesystem (if only as a directory stub to be used as a mountpoint), so reading it isn't leaving that filesystem. Reading anything *in* it would be. Just a thought. And a good one. Yes, that's it. It isn't crossing the mount point, but the mount point is part of the root filesystem. I find it quite astonishing that /proc would deliberately behave differently to *every other* filesystem available. The mountpoint should belong to the filesystem mounted on it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On Nov 18, 2011, at 11:27 AM, Robert Bonomi wrote: See the output of 'mount(8)' for the names of all the mounted filesystems on your machine. $ mount | grep proc procfs on /proc (procfs, local) *NOTE*WELL* that '/proc' is *not* a separate filesystem. It is merely a _directory_ with a bunch of 'special' files in it. I'm confused here. In what way isn't /proc a separate filesystem? It's even called procfs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On Fri, Nov 18, 2011 at 9:27 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: I find it quite astonishing that /proc would deliberately behave differently to *every other* filesystem available. The mountpoint should belong to the filesystem mounted on it. I have an idea what you mean by belong to in this case and - if I'm right, you're wrong :-) A mount point has an inode in the parent filesystem, right? Good, glad we cleared that up. Unless you set the 'nodump' flag, and tell tar/gtar/tarsnap/dump to honor the flag, the archive will have an entry for the mount point. The 'one-file-system' flags tells gtar not to traverse mount points, but it will certainly see the mount point and include it in the archive, along with its modes, flags, atime, mtime, etc. etc. If those changed between the time if took a peek at the directory and the time it attempted to include it in the archive, you'll see those advisory warnings (which may be ignored in this case). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
On Fri, 18 Nov 2011, Kirk Strauser wrote: On Nov 18, 2011, at 11:27 AM, Robert Bonomi wrote: See the output of 'mount(8)' for the names of all the mounted filesystems on your machine. $ mount | grep proc procfs on /proc (procfs, local) *NOTE*WELL* that '/proc' is *not* a separate filesystem. It is merely a _directory_ with a bunch of 'special' files in it. I'm confused here. In what way isn't /proc a separate filesystem? It's even called procfs. I just went to an 8.1 system as root and did: umount /proc and /proc dismounted leaving an empty directory in route. I then went mount /proc and /proc was mounted again, using the parameters in /etc/fstab. Surely that means that going from / to /proc is crossing a filesystem boundary. To me that suggests it is a separate filesystem, and typically /proc is filled with stuff that you wouldn't want to recurse through, so I wouldn't think it a good candidate for special casing as non-mounted. Daniel Feenberg NBER ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shouldn't GNU tar be ignoring /proc with --one-file-system?
Kirk Strauser k...@strauser.com wrote: On Nov 18, 2011, at 11:27 AM, Robert Bonomi wrote: See the output of 'mount(8)' for the names of all the mounted filesystems on your machine. $ mount | grep proc procfs on /proc (procfs, local) *NOTE*WELL* that '/proc' is *not* a separate filesystem. It is merely a _directory_ with a bunch of 'special' files in it. I'm confused here. In what way isn't /proc a separate filesystem? It's even called procfs. It's Bonomi who is confused. I suspect he doesn't have procfs configured -- so of course its mountpoint is just a directory -- *on his system*. The OP _does_ have procfs configured, or the question wouldn't have arisen. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Shouldn't GNU tar be ignoring /proc with --one-file-system?
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Daniel Staal Sent: Friday, November 18, 2011 18:00 To: freebsd-questions@freebsd.org Subject: Re: Shouldn't GNU tar be ignoring /proc with --one-file- system? On Fri, November 18, 2011 10:34 am, Kirk Strauser wrote: I use Amanda to make nightly backups of a bunch of servers using GNU tar. However, gtar doesn't seem to respect its --one-file-system flag with /proc. Amanda runs a variation of this command: # /usr/local/bin/gtar --create --file - --directory / --one-file-system --sparse --ignore-failed-read --totals . /dev/null /usr/local/bin/gtar: ./proc: file changed as we read it Before I file a bug report, can anyone think of a legitimate reason why gtar would be touching /proc at all? Just a guess, really but: /proc is a file on /. /proc/* are files on /proc. The former is still on the root filesystem (if only as a directory stub to be used as a mountpoint), so reading it isn't leaving that filesystem. Reading anything *in* it would be. Just a thought. However, the file /proc on fs / should not be changing since a filesystem /proc is mounted over it. The message ./proc: file changed as we read it indicates whatever /proc it is trying to read did change... -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk MediaMonks B.V. (www.mediamonks.com) Please quote relevant replies in correspondence. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
file lose inode in Memory-Based file system.
my syetem is FreeBSD 8.2. i build a memory disk : mdmfs -s 10G -i 512 -o rw md1 /home/test1 After a period of time，some file in the memory disk lose their inode: #ls 90020595.o #ls -l 90020595.o ls: 90020595.o: No such file or directory it seem the inode of this file was lost. how to solve this problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On 08/07/2011 23:04, Gary Kline wrote:
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote:
Date: Fri, 08 Jul 2011 10:01:45 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: freebsd-questions@freebsd.org
On 08/07/2011 08:25, Doug Hardie wrote:
On 7 July 2011, at 22:58, Gary Kline wrote:
Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file
not found
Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c
/var/named/etc/namedb/named.conf
The first one that fails is looking for /etc/named.conf. The second
one shows its in /var/named/etc/named/named.conf
Those are different locations. I suspect you have named_flags setup
in rc.conf pointing to /etc/namedb/named.conf rather than the right
location. Its also possible that its not set in rc.conf but defaults
in either the rc script or /etc/rc.d/named. On my system it appears
to default in /etc/rc.d/named.
FreeBSD defaults to running named chrooted. /etc/namedb is actually a
symbolic link:
hi matthew,
i found an in-depth post you wrote re mtree yesterday ( 07july ),
but i figured it was over my head in resetting anything i might need
to reset. i was going to write you offlist. decided to ask the
entire list.
% ls -la /etc/namedb
lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ -
/var/named/etc/namedb
so the files referenced are in fact exactly the same file. However, the
flags from the log extract don't look like the defaults to me. (I'm
running the dns/bind98 port, and the equivalent info from the log line
is '-t /var/named -u bind')
i was using bind98 rather than the earlier bind9 which is out of
date. but bind98 gave me troubles with the rndc.key and other, so i
chose to go back with what worked. --first thing is to get this
working with the older bind9. FWIW, both bind9's given me the same
error and failure. i have walked thru the named script to the point
where it creates the symlink. regardless, i cannot understand the
error and failure messages. i only know that my kill -9 and my
initialization by hand work.
Gary, what named related settings do you have in /etc/rc.conf? You
almost certainly don't need anything more than:
named_enable=YES
and perhaps
syslogd_flags=-ss -l /var/named/var/run/log
so named can log to the system syslog.
Hmmm [c]. as you may have seen in my post to Doug H. i only have
--
named_enable=YES
named_program=/usr/local/sbin/named
named_pidfile=/var/run/named/pid
OK. The good news is that the configuration that works for the system
built-in version of named will work for the dns/bind98 port with very
minor changes, if any.
First: where everything should live
/etc/namedb/named.conf --- named's config file
/etc/namedb/master --- zone files this server is master for
/etc/namedb/slave --- zone files this server slaves from
another master (rw by named)
/etc/named/working --- named's working directory (rw by named)
/etc/rndc.conf --- config file for rndc
There are various other files and directories under /etc/namedb which
you may or may not need depending on how you configure named; in any
case, just leave them in their default locations and with the
permissions the system gives them. (You can use mtree(8) to fix them up
if necessary -- but that's a whole other posting)
Now, although named defaults to running chrooted into /var/namedb, you
don't need to mention that path explicitly anywhere in the config. In
fact, you should think about the configuration as if there was no
chrooting happening at all.
Second: rc.conf settings
named_enable=YES
syslogd_flags=-ss -l /var/named/var/run/log
should be all you need to use the built-in version of named.
Third: rndc configuration
Generate a new rndc key and a config file by:
# rndc-confgen /etc/named/rndc.conf
This should create a new file /etc/namedb/rndc.conf preconfigured to
work with the named instance on the localhost. Look at the text of
the file -- commented out there's a chunk of stuff to copy into
named.conf So let's do that.
If the file contains:
# key rndc-key {
# algorithm hmac-md5;
# secret 0ABCDE123+45+67890==;
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { rndc-key; };
# };
Then copy that without the '#' quotes into named.conf In fact, I find
it helps to add a control for access to ::1 as well. So add this text
to /etc/namedb/named.conf:
key rndc-key {
algorithm hmac-md5;
secret 0ABCDE123+45+67890==;
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { rndc-key; };
inet ::1 port 953
allow { ::1; } keys { rndc-key; };
};
Fourth: set up named.conf
As I don't no much about the config you want, I'm going to have to keep
this to generalities.
In the options section you should
Re: DNS and file system messed up...
On Jul 8, 2011, at 9:54 PM, Gary Kline wrote: On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on :: 1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Gary, Theres probably an /etc/rc.conf line to fix these but what I always do is simply symlink /etc/namedb/rndc.key to /etc/rndc.key # ln -s /etc/namedb/rndc.key /etc/rndc.key I actually use rndc.conf on my systems but I think the names and files are interchangeable. Dan Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel :: 1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Sat, Jul 09, 2011 at 07:49:43AM -0600, Dan Busarow wrote: Date: Sat, 9 Jul 2011 07:49:43 -0600 From: Dan Busarow d...@buildingonline.com Subject: Re: DNS and file system messed up... To: Gary Kline kl...@thought.org Cc: freebsd-questions@freebsd.org, Gary Kline kl...@magnesium.net X-Mailer: Apple Mail (2.753.1) On Jul 8, 2011, at 9:54 PM, Gary Kline wrote: On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on ::1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Gary, Theres probably an /etc/rc.conf line to fix these but what I always do is simply symlink /etc/namedb/rndc.key to /etc/rndc.key # ln -s /etc/namedb/rndc.key /etc/rndc.key I actually use rndc.conf on my systems but I think the names and files are interchangeable. Dan No joy. I just tried that from /etc: lrwxr-xr-x 1 root wheel21 Jul 9 11:18 namedb - /var/named/etc/namedb lrwxr-xr-x 1 root wheel20 Jul 9 11:17 rndc.key - /etc/namedb/rndc.key and I find the same warnings/complainnts as earlier. The good news, still, is that bin9 works. But I still get a lookup error from the -questions list in /var/log/maillog, so nothing is getting thru to the list from here at thought.org. FWIW: Yesterday, I got the latest 7.3 upgrade and compiled it. I habe NOT yet installed anything new because the last thing i want to do is lose my own link with the real world . :-) * 0.5 your thoughts what I should try next, please? gary Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel ::1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Sat, Jul 09, 2011 at 09:14:21AM +0100, Matthew Seaman wrote:
Date: Sat, 09 Jul 2011 09:14:21 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: Gary Kline kl...@thought.org
CC: freebsd-questions@freebsd.org
On 08/07/2011 23:04, Gary Kline wrote:
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote:
Date: Fri, 08 Jul 2011 10:01:45 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: freebsd-questions@freebsd.org
On 08/07/2011 08:25, Doug Hardie wrote:
On 7 July 2011, at 22:58, Gary Kline wrote:
Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf:
file not found
Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c
/var/named/etc/namedb/named.conf
The first one that fails is looking for /etc/named.conf. The second
one shows its in /var/named/etc/named/named.conf
Those are different locations. I suspect you have named_flags setup
in rc.conf pointing to /etc/namedb/named.conf rather than the right
location. Its also possible that its not set in rc.conf but defaults
in either the rc script or /etc/rc.d/named. On my system it appears
to default in /etc/rc.d/named.
FreeBSD defaults to running named chrooted. /etc/namedb is actually a
symbolic link:
hi matthew,
i found an in-depth post you wrote re mtree yesterday ( 07july ),
but i figured it was over my head in resetting anything i might need
to reset. i was going to write you offlist. decided to ask the
entire list.
% ls -la /etc/namedb
lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ -
/var/named/etc/namedb
so the files referenced are in fact exactly the same file. However, the
flags from the log extract don't look like the defaults to me. (I'm
running the dns/bind98 port, and the equivalent info from the log line
is '-t /var/named -u bind')
i was using bind98 rather than the earlier bind9 which is out of
date. but bind98 gave me troubles with the rndc.key and other, so i
chose to go back with what worked. --first thing is to get this
working with the older bind9. FWIW, both bind9's given me the same
error and failure. i have walked thru the named script to the point
where it creates the symlink. regardless, i cannot understand the
error and failure messages. i only know that my kill -9 and my
initialization by hand work.
Gary, what named related settings do you have in /etc/rc.conf? You
almost certainly don't need anything more than:
named_enable=YES
and perhaps
syslogd_flags=-ss -l /var/named/var/run/log
so named can log to the system syslog.
Hmmm [c]. as you may have seen in my post to Doug H. i only have
--
named_enable=YES
named_program=/usr/local/sbin/named
named_pidfile=/var/run/named/pid
OK. The good news is that the configuration that works for the system
built-in version of named will work for the dns/bind98 port with very
minor changes, if any.
First: where everything should live
/etc/namedb/named.conf --- named's config file
/etc/namedb/master --- zone files this server is master for
/etc/namedb/slave --- zone files this server slaves from
another master (rw by named)
/etc/named/working --- named's working directory (rw by named)
/etc/rndc.conf --- config file for rndc
There are various other files and directories under /etc/namedb which
you may or may not need depending on how you configure named; in any
case, just leave them in their default locations and with the
permissions the system gives them. (You can use mtree(8) to fix them up
if necessary -- but that's a whole other posting)
Now, although named defaults to running chrooted into /var/namedb, you
don't need to mention that path explicitly anywhere in the config. In
fact, you should think about the configuration as if there was no
chrooting happening at all.
Second: rc.conf settings
named_enable=YES
syslogd_flags=-ss -l /var/named/var/run/log
should be all you need to use the built-in version of named.
Third: rndc configuration
Generate a new rndc key and a config file by:
# rndc-confgen /etc/named/rndc.conf
This should create a new file /etc/namedb/rndc.conf preconfigured to
work with the named instance on the localhost. Look at the text of
the file -- commented out there's a chunk of stuff to copy into
named.conf So let's do that.
If the file contains:
# key rndc-key {
# algorithm hmac-md5;
# secret 0ABCDE123+45+67890==;
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { rndc-key; };
# };
Then copy that without the '#' quotes into named.conf In fact, I find
it helps to add a control for access to ::1 as well. So add this text
to /etc/namedb
Re: DNS and file system messed up...
On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: DNS and file system messed up...
On Jul 8, 2011, at 3:01 AM, Matthew Seaman wrote: On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/ named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c / var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. Actually /etc/named.conf is NOT the same as /etc/namedb/named.conf ergo it is not the same as /var/named/etc/ namedb/named.conf Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 12:25:34AM -0700, Doug Hardie wrote: Date: Fri, 8 Jul 2011 00:25:34 -0700 From: Doug Hardie bc...@lafn.org Subject: Re: DNS and file system messed up... To: Gary Kline kl...@thought.org Cc: FreeBSD Mailing List freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1084) On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. Hm.. i understand most of this. grep -r from /etc found something i've never uderstood. chroot stuff. to me, root is always / and root's home is /rrot. I've never dug deeper. here is the named stuff in /etc/defaults dir: named_enable=NO # Run named, the DNS server (or NO). named_program=/usr/sbin/named # Path to named, if you want a different one. #named_flags=-c /etc/namedb/named.conf # Uncomment for named not in /usr/sbin named_pidfile=/var/run/named/pid # Must set this in named.conf as well named_uid=bind# User to run named as named_chrootdir=/var/named# Chroot directory (or not to auto-chroot it) named_chroot_autoupdate=YES # Automatically install/update chrooted # components of named. See /etc/rc.d/named. named_symlink_enable=YES # Symlink the chrooted pid file in my /etc/rc.conf file are the 3 named lines: named_enable=YES named_program=/usr/local/sbin/named named_pidfile=/var/run/named/pid I dont see anything here that could be messing me up unless by using the default lines, something is going waaay South. Lastly, has the /etc/rc.d/named script changed in the past year or two? thankee -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote: Date: Fri, 08 Jul 2011 10:01:45 +0100 From: Matthew Seaman m.sea...@infracaninophile.co.uk Subject: Re: DNS and file system messed up... To: freebsd-questions@freebsd.org On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: hi matthew, i found an in-depth post you wrote re mtree yesterday ( 07july ), but i figured it was over my head in resetting anything i might need to reset. i was going to write you offlist. decided to ask the entire list. % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') i was using bind98 rather than the earlier bind9 which is out of date. but bind98 gave me troubles with the rndc.key and other, so i chose to go back with what worked. --first thing is to get this working with the older bind9. FWIW, both bind9's given me the same error and failure. i have walked thru the named script to the point where it creates the symlink. regardless, i cannot understand the error and failure messages. i only know that my kill -9 and my initialization by hand work. Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Hmmm [c]. as you may have seen in my post to Doug H. i only have -- named_enable=YES named_program=/usr/local/sbin/named named_pidfile=/var/run/named/pid Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Date: Fri, 8 Jul 2011 07:27:12 -0600 From: Dan Busarow d...@buildingonline.com Subject: Re: DNS and file system messed up... To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.753.1) On Jul 8, 2011, at 3:01 AM, Matthew Seaman wrote: On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. Actually /etc/named.conf is NOT the same as /etc/namedb/named.conf ergo it is not the same as /var/named/etc/namedb/named.conf Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on ::1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel ::1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Thu, Jul 07, 2011 at 06:00:42PM +, Gary Kline wrote: Date: Thu, 7 Jul 2011 18:00:42 + From: Gary Kline kl...@magnesium.net Subject: DNS and file system messed up... To: FreeBSD Mailing List freebsd-questions@FreeBSD.ORG Guys, I'd be much obliged to learn why /etc/rc.named start fails. This has been going on for months. For some reason freebsd.org doesn't recognize part of my domain, so I'm writing from my backup site, magnesium net. I did *somrthing* that keeps /etc/rc.d/named from working correctly. On the second line below the ^+, you'll see a none:0:/etc/named.conf from messages. The only way I can exec bind9 is by first doing a kill -9, then explicitly starting named and then, with the -c switch , aiming it at my *real* named.conf. I don't want to finish my new/latest install of 7.3 until I understand this screwup. Nobody has any clues to the capture output? I'm surprised. -g # sh /etc/rc.d/named start Starting named. + # tail /var/log/messages Jul 7 10:16:33 ethic named[54366]: starting BIND 9.3.6-P1 -t /var/named -u bind Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:16:33 ethic named[54366]: loading configuration: file not found Jul 7 10:16:33 ethic named[54366]: exiting (due to fatal error) # tail /var/log/messages # kill -9 `head -1 /var/run/named/pid` # /usr/local/sbin/named -c /var/named/etc/namedb/named.conf Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jul 7 10:17:56 ethic named[54371]: command channel listening on 127.0.0.1#953 Jul 7 10:17:56 ethic named[54371]: command channel listening on ::1#953 Jul 7 10:17:56 ethic named[54371]: running + -- Gary Kline Seattle BSD Users' Group (seabug) | kl...@magnesium.net Thought Unlimited Org's Alternate Email Site http://www.magnesium.net/~kline To live is not a necessity; but to live honorably...is a necessity. -Kant -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cfs (cryptographic file system) ?
No problem:
I looked up my solution to the problem because I submitted a patch to fix
things. It's here (ports pr #155788):
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155788
After this you should be able to create an encrypted filesystem with cmkdir and
attach it with cattach and detach it with cdetach.
-- Chris
On May 17, 2011, at 6:53 AM, Alano Conraz wrote:
I tried this and it seems to work.
Thank you very much for your help!
Have a good day.
While still being useful cfsd is old and doesn't conform to the latest
practices in nfs servers. In particular, it doesn't: use tcp, use IPv6, or do
nfs v3 or later.
I changed the line in the .../rc.d/cfsd script that came with the port to the
following:
mount -o port=$cfsd_port,nfsv2,udp 127.0.0.1:${cfsd_bootstrap}
$cfsd_mountpoint
I changed the mount to use udp and nfsv2. I also coded the localhost address
rather than the name. Finally, I made the bootstrap and the mountpoint
controllable via configuration variables. I'm pretty sure that I sent these
modifications to the cfs port maintainer as a patch to the port. I also
probably included a KEYWORD: shutdown in the port to get by an annoying
warning and the second startup.
-- Chris Hilton
Chris Hilton e: chris|at|vindaloo|dot|com
The pattern juggler lifts his hand; The orchestra begin.
As slowly turns the grinding wheel in the court of the crimson king.
-- Ian McDonald / Peter Sinfield
Chris Hilton tildeChris -- http://myblog.vindaloo.com
e: -- chris /at/ vindaloo /dot/ com
.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.--.~~.
I'm on the outside looking inside, What do I see?
Much confusion, disillusion, all around me.
-- Ian McDonald / Peter Sinfield
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cfs (cryptographic file system) ?
(Sorry for the double email, i made a mistake) I tried again launching nfsd, here is what I did (killing all these process before) : rpcbind nfsd -u -t -n 6 mountd -r and then : /usr/local/etc/rc.d/cfsd onestart But i still got the same error : [tcp] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused [tcp6] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused I tried to access /usr/local/cfsd-bootstrap from another freebsd client (adding its IP address in /etc/exports at the end of the line I already had), and it worked, so it doesn't seem to be a nfs problem... Do you have another clue for me ? Thanks. And I always get the same error : [tcp] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused and the same with [tcp6] You need to start nfsd? - Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to use cfs (cryptographic file system) ?
Hello, In order to test cfs, i tried to set up a ciphered directory. Unfortunatelly, i failed... Documentation doesn't seem to be up-to-date, so it does not help much. Here is what I did : pkg_add cfs package address echo /usr/local/cfs-bootstrap localhost /etc/exports mkdir /crypt rcpbind -h 127.0.0.1 mountd -h 127.0.0.1 and then : /usr/local/etc/rc.d/cfsd onestart And I always get the same error : [tcp] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused and the same with [tcp6] Could you help me ? I had a look to mailing archives, but with no success. Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to use cfs (cryptographic file system) ?
Hello, In order to test cfs, i tried to set up a ciphered directory. Unfortunatelly, i failed... Documentation doesn't seem to be up-to-date, so it does not help much. Here is what I did : pkg_add cfs package address echo /usr/local/cfs-bootstrap localhost /etc/exports mkdir /crypt rcpbind -h 127.0.0.1 mountd -h 127.0.0.1 and then : /usr/local/etc/rc.d/cfsd onestart And I always get the same error : [tcp] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused and the same with [tcp6] Could you help me ? I had a look to mailing archives, but with no success. Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cfs (cryptographic file system) ?
ALANO CONRAZ wrote: And I always get the same error : [tcp] localhost:/usr/local/cfsd-bootstrap: nfsd: RCPROG_NFS: RPC: Remote system error - Connection refused and the same with [tcp6] You need to start nfsd? - Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
