search for: ufs2

...om ldlinux.bin, and check if it exceeds the limit. > > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > > Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. > > > > Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, > > thus it can't exceed the limit, otherwise the superblock would be corrupted. Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not installed to the first sector where the first superblock is located. >...

Hello, I'm running centos5 with the centosplus kernel v2.6.18-8.1.8.el5 and i'm trying to read a drive that has a ufs2 partition on it. It was originally in a FreeBSD machine and has some data i'd like to get at. Googling indicated this should work with the command: mount -r -t ufs -o ufstype=ufs2 <device> <mountpoint> device is /dev/hdb5 and mountpoint is /mnt. I'm getting an error unknown...

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 71 +++++++++--- extlinux/ufs.h | 26 ++++ extlinux/ufs_fs.h | 307 ++++++++++++++++++++++++++++++++++++++++++...

...eeds > the limit. > > > ldlinux.sys must fit between the bootsector and two copies of ADV whose > size may vary. > > > Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * > ADV_SIZE - 512. > > > > > > Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys > being installed on the 0-64k range, > > > thus it can't exceed the limit, otherwise the superblock would be > corrupted. > > Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not > installed to the first sector where the first...

...G HOLEY # no space allocated $ time dd <SPACY >/dev/null bs=1m # A1 $ time dd <HOLEY >/dev/null bs=1m # A2 $ time cat SPACY >/dev/null # B1 $ time cat HOLEY >/dev/null # B2 $ time md5 SPACY # C1 $ time md5 HOLEY # C2 I have summarized the results below. ZFS UFS2 Elapsed System Elapsed System Test dd SPACY bs=1m 110.26 22.52 340.38 19.11 A1 dd HOLEY bs=1m 22.44 22.41 24.24 24.13 A2 cat SPACY 119.64 33.04 342.77 17.30 B1 cat HOLEY 222.85 222.08 22.91 22.41 B2 md5 SPACY 210.01 77.46 337.51 25.54 C1 md5 HOLEY 856.39 801.21 8...

Hi Genec, On Sun, May 25, 2014 11:27 am, Gene Cumm wrote: > Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not > installed to the first sector where the first superblock is located. I have no much experience with UFS2 filesystem. I've just took a quick look at its internals and I can see that UFS2 places its superblock at either 64KiB or 256KiB (dependin...

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. UFS2 has no cow feature unlike BTRFS. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 79 ++++++++++--- extlinux/ufs.h | 26 ++++ extlinux/ufs_fs.h | 307 +++...

Hi, This is my first post to this list. I have been backing up some files with rsync from My Mac OS X 10.4.7 machine, which uses HFS+ filesystem to a FreeBSD 6.1-RELEASE machine, which uses UFS2 filesystem. They go across a 100-base-T lan, which has little or no traffic on it. On my Mac, I mount the nfs exported volume on the FreeBSD machine with: $ mount -t nfs moe:/backup /Users/Charles/mnt I recently had to restore these files, and not all of them survived the trip. I should menti...

On Fri, 12 Jul, at 08:31:27PM, Raphael S.Carvalho wrote: > @@ -575,7 +594,7 @@ bail: > return 1; > } > > -/* btrfs has to install the ldlinux.sys in the first 64K blank area, which > +/* btrfs/ufs2 has to install the ldlinux.sys in the first 64K blank area, which > is not managered by btrfs tree, so actually this is not installed as files. > since the cow feature of btrfs will move the ldlinux.sys every where */ > int btrfs_install_file(const char *path, int devfd, struct st...

HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no

...your kernel with that option enabled. Further information can be found in the link below: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Installing syslinux on an UFS image: - Install extl...

...your kernel with that option enabled. Further information can be found in the link below: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Installing syslinux on an UFS image: - Install extl...

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit, otherwise the superblock would be corrupted. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/Makefile | 1 + core/ldlinux_limit.pl | 39 ++++++++++++++++++++...

...s->block_shift - UFS_SB(fs)->addr_shift; + ptrs_per_blk = fs->block_size >> UFS_SB(fs)->addr_shift; + + indir_blks = ptrs_per_blk; + double_blks = ptrs_per_blk << shft_per_blk; + triple_blks = double_blks << shft_per_blk; + } + + /* + * direct blocks + * (UFS2_ADDR_SHIFT) is also used for UFS1 because its direct ptr array + * was extended to 64 bits. + */ + if (block < UFS_DIRECT_BLOCKS) + return scan_set_nblocks((uint8_t *) PVT(inode)->direct_blk_ptr, + block, UFS2_ADDR_SHIFT, + UFS_DIRECT_BLOCKS - block, nblocks); + + /* indir...

...s->block_shift - UFS_SB(fs)->addr_shift; + ptrs_per_blk = fs->block_size >> UFS_SB(fs)->addr_shift; + + indir_blks = ptrs_per_blk; + double_blks = ptrs_per_blk << shft_per_blk; + triple_blks = double_blks << shft_per_blk; + } + + /* + * direct blocks + * (UFS2_ADDR_SHIFT) is also used for UFS1 because its direct ptr array + * was extended to 64 bits. + */ + if (block < UFS_DIRECT_BLOCKS) + return scan_set_nblocks((uint8_t *) PVT(inode)->direct_blk_ptr, + block, UFS2_ADDR_SHIFT, + UFS_DIRECT_BLOCKS - block, nblocks); + + /* indir...

Hi all, I am playing with a test box at the moment running a Samba 2.2.7a domain on FreeBSD 5.0. I wish to enable ACLs, but I am not exactly sure what I am supposed to expect once they are enabled. I have created a UFS2 partition and enabled ACL support using tunefs. Since doing that, I have been able to connect to the Samba shares and modify ACLs, but so far the only things I have been able to accomplish are changing ownership, and modifying the o/g/u permissions. As I understand it, because UFS2 supports ACLs,...

...adv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit, otherwise the superblock would be corrupted. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> Suggested-by: Matt Fleming <matt at console-pimps.org> --- core/Makefile...

Any progress here? Does anyone know if this will be fixed in 7.1 latest, or should we start looking for different backup solution (in this case I would suggest to remove dump from the source tree - having a backup tool that doesn't work is worse than having none). After upgrading we basically cannot backup our servers. Shouldn't this issue be on

I am building a tool to identify the file that has a specific LBA. The approach I am using is to search through each inode from number 2 up. This approach works well with UFS1 file systems as then preinitialize all the inodes. However, UFS2 does lazy inode initialization so there are always some that are basically garbage. I have not found any relaiable way to determine from the inode contents if it is in use or not. I suspect that information is in the inode bit map. However, I haven't found any way to access that....

...n you need to enable it and recompile your kernel. Further information can be found here: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Installing syslinux on an UFS image: 1- The UFS sup...