HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Large disk array on Solaris 7
Disk Enclosures
1827808
Members
12436
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2001 01:13 PM
11-19-2001 01:13 PM
Large disk array on Solaris 7
No, I am not a new user. I've done newfs probably hundreds
of times. But, I've never had to futz around with obscure
parameters because the device geometry was insane.
I want to get a file system made that
doesn't require 4096 byte fragments. Is that too much to ask?
I would think that there is some combination of cylinders,
heads, and sectors that should give that result, but I don't
have time to search for it.
tahoe# newfs -m 1 -o time /dev/rdsk/c2t8d0s2
newfs: construct a new file system /dev/rdsk/c2t8d0s2: (y/n)? y
With 16129 sectors per cylinder, minimum cylinders per group is 16
and the fragment size to be changed from 0 to 4096
With these parameters, it returns immediately, seemingly doing
nothing -f 4096 to specify the fragment size, like:
tahoe# newfs -f 4096 -m 1 -o time /dev/rdsk/c2t8d0s2
This worked, or seemed to.
The problem now is that it I am losing a lot of space when I have
directories with lots of little files.
of times. But, I've never had to futz around with obscure
parameters because the device geometry was insane.
I want to get a file system made that
doesn't require 4096 byte fragments. Is that too much to ask?
I would think that there is some combination of cylinders,
heads, and sectors that should give that result, but I don't
have time to search for it.
tahoe# newfs -m 1 -o time /dev/rdsk/c2t8d0s2
newfs: construct a new file system /dev/rdsk/c2t8d0s2: (y/n)? y
With 16129 sectors per cylinder, minimum cylinders per group is 16
and the fragment size to be changed from 0 to 4096
With these parameters, it returns immediately, seemingly doing
nothing -f 4096 to specify the fragment size, like:
tahoe# newfs -f 4096 -m 1 -o time /dev/rdsk/c2t8d0s2
This worked, or seemed to.
The problem now is that it I am losing a lot of space when I have
directories with lots of little files.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP