Ian Collins <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Are these I/O errors written to stdout or stderr or where?
>
> Yes, stderr.
OK, good, thanks.
> You will not be able top open the file.
What?! Even if there are errors I want to still be able to read
Ian Collins <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > I couldn't see anything there describing either how to verify the
> > checksums of individual files or why that would be impossible.
>
> If you can read the file, the checksum is OK. If it were n
"Scott Laird" <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 25, 2008 at 1:57 PM, Marcus Sundman <[EMAIL PROTECTED]>
> wrote:
> > I don't want to scrub several TiB of data just to verify a 2 MiB
> > file. I want to verify just the data of that file. (Well, I
"Johan Hartzenberg" <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 25, 2008 at 6:49 PM, Marcus Sundman <[EMAIL PROTECTED]>
> wrote:
> > Richard Elling <[EMAIL PROTECTED]> wrote:
> > > Marcus Sundman wrote:
> > > > How can I verify the checksum
Richard Elling <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > How can I verify the checksums for a specific file?
>
> ZFS doesn't checksum files.
AFAIK ZFS checksums all data, including the contents of files.
> So a file does not have a checksum to verify.
How can I verify the checksums for a specific file?
- Marcus
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
"James C. McPherson" <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > [...]
> blinder:jmcp $ for dev in `awk -F'"' '/sd/ {print
> $2}' /etc/path_to_inst`; do prtconf -v /devices/$dev|egrep -i
> "id1|dev.dsk.*s2" ; done
>
"James C. McPherson" <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > I couldn't figure out which controller got which numbers so I had
> > to disconnect drives one by one
>
> I'm interested in what you did to figure out your drive
> lo
A Darren Dunham <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 11, 2008 at 03:19:49AM +0300, Marcus Sundman wrote:
> > I've used format's "volname" command to give labels to my drives
> > according to their physical location. I did quite a lot of work
> >
Hi
I've used format's "volname" command to give labels to my drives
according to their physical location. I did quite a lot of work
labeling all my drives (I couldn't figure out which controller got
which numbers so I had to disconnect drives one by one, and they're not
hotpluggable => lot's of re
"Brandon High" <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 27, 2008 at 4:02 PM, Marcus Sundman <[EMAIL PROTECTED]>
> wrote:
> > So, is it possible to create a 5 * 1 TB raidz with 4 disks (i.e.,
> > with one disk offline)?
>
> [...]
> 1. Create a spars
Hi,
I'm about to convert my 3 * 1 TB raidz to a 5 * 1 TB raidz. Since raidz
can't be grown like that I have to find some place to move the data to
temporarily while I reformat the raidz. However, I'm short on disk
space (which is why I'm adding 2 new disks).
So, is it possible to create a 5 * 1 T
> > 1. In zfs can you currently add more disks to an existing raidz?
> > This is important to me as i slowly add disks to my system one at a
> > time.
>
> No
Is this being worked on? Is it even planned? (I've looked at a bunch of
FAQs and searched some mailing lists but I can't find the answers s
"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> > Do you happen to know where programs in (Open)Solaris look when they
> > want to know how to encode text to be used in a filename? Is it
> > LC_CTYPE?
>
> In general, they don't. Command-line utilities just use the sequence
> of bytes entered by the
Chris Gilligan <[EMAIL PROTECTED]> wrote:
> 2. in a raidz do all the disks have to be the same size?
Related question:
Does a raidz have to be either only full disks or only slices, or can
it be mixed? E.g., can you do a 3-way raidz with 2 complete disks and
one slice (of equal size as the disks)
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Bart Smaalders <[EMAIL PROTECTED]> wrote:
> >> UTF8 is the answer here. If you care about anything more than
> >> simple ascii and you work in more than a single locale/encoding,
&g
[EMAIL PROTECTED] (Joerg Schilling) wrote:
> Marcus Sundman <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] (Joerg Schilling) wrote:
> > > [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
> >
> > Unicode is not an encoding, but you probably mean "the l
[EMAIL PROTECTED] (Joerg Schilling) wrote:
> [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
Unicode is not an encoding, but you probably mean "the low 8 bits of
UCS-2" or "the first 256 codepoints in Unicode" or somesuch.
Regards,
Marcus
___
zfs-
"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> > OK, thanks. I still haven't got any answer to my original question,
> > though. I.e., is there some way to know what text the
> > filename is, or do I have to make a more or less wild guess what
> > encoding the program that created the file used?
>
>
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Bart Smaalders <[EMAIL PROTECTED]> wrote:
> >>> I'm unable to find more info about this. E.g., what does "reject
> >>> file names" mean in practice? E.g., if a pro
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> > I'm unable to find more info about this. E.g., what does "reject
> > file names" mean in practice? E.g., if a program tries to create a
> > file using an utf8-incompatible filename, what happens? Does the
> > fopen() fail? Would this normally be a probl
So, I set utf8only=on and try to create a file with a filename that is
a byte array that can't be decoded to text using UTF-8. What's supposed
to happen? Should fopen(), or whatever syscall 'touch' uses, fail?
Should the syscall somehow escape utf8-incompatible bytes, or maybe
replace them with ?s
"Wee Yeh Tan" <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 27, 2008 at 10:42 PM, Marcus Sundman <[EMAIL PROTECTED]>
> wrote:
> > Darren J Moffat <[EMAIL PROTECTED]> wrote:
> > > Marcus Sundman wrote:
> > > > Nicolas Williams <[EMAIL
Darren J Moffat <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Nicolas Williams <[EMAIL PROTECTED]> wrote:
> >> On Wed, Feb 27, 2008 at 05:54:29AM +0200, Marcus Sundman wrote:
> >>> Nathan Kroenert <[EMAIL PROTECTED]> wrote:
> >>&
Darren J Moffat <[EMAIL PROTECTED]> wrote:
> See the description of the normalization and utf8only properties in
> the zfs(1) man page.
>
> I think this might help you.
>
> normalization =none | formD | formKCf
That's apparently only for comparisons, so I don't see how it's
relevant.
>
Nicolas Williams <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 27, 2008 at 05:54:29AM +0200, Marcus Sundman wrote:
> > Nathan Kroenert <[EMAIL PROTECTED]> wrote:
> > > Are you indicating that the filesystem know's or should know what
> > > an applicat
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Are path-names text or raw data in zfs? I.e., is it possible to know
> > what the name of a file/dir/whatever is, or do I have to make more
> > or less wild guesses what encoding is u
Nathan Kroenert <[EMAIL PROTECTED]> wrote:
> Are you indicating that the filesystem know's or should know what an
> application is doing??
Maybe "snapshot file whenever a write-filedescriptor is closed" or
somesuch?
- Marcus
___
zfs-discuss mailing li
Are path-names text or raw data in zfs? I.e., is it possible to know
what the name of a file/dir/whatever is, or do I have to make more or
less wild guesses what encoding is used where?
- Marcus
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
ht
Mark Ashley <[EMAIL PROTECTED]> wrote:
> It's simply a shell grokking issue, when you allow your (l)users to
> self name your files then you will have spaces etc in the filename
> (breaks shell arguments). In this case the '[E]' is breaking your
> command line argument grokking.
Can't be, because
Tim Cook <[EMAIL PROTECTED]> wrote:
> I'm currently running the asus K8N-LR, and it works wonderfully.
Thanks, but socket 939 is cold dead and buried. S939 CPUs are very
expensive. DDR is over twice as expensive as DDR2. I can't tell if the
motherboard is expensive or not because I just can't find
Marcus Sundman <[EMAIL PROTECTED]> wrote:
> Richard Elling <[EMAIL PROTECTED]> wrote:
> > It may be less expensive to purchase a new motherboard with 6 SATA
> > ports on it.
>
> Sure, but which one? I've been trying to find one for many, many
> mo
Richard Elling <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Kava <[EMAIL PROTECTED]> wrote:
> >
> >> Can anyone recommend a cheap (but reliable) SATA PCI or PCIX card?
> >>
> >
> > Why would you get a PCI-X card for
Let's say I have two 300 GB drives and one 500 GB drive. Can I put a
RAID-Z on the three drives and a separate partition on the last 200 GB
of the 500 GB drive?
- Marcus
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org
Kava <[EMAIL PROTECTED]> wrote:
> Can anyone recommend a cheap (but reliable) SATA PCI or PCIX card?
Why would you get a PCI-X card for a home NAS? I don't think I've ever
seen a non-server motherboard with PCI-X. Are you sure you don't want a
PCI-E card instead?
Anyway, if someone is aware of so
> So I was hoping that this board would work: [...]GA-M57SLI-S4
I've been looking at that very same board for the very same purpose. It
has 2 gb nics, 6 sata ports, supports ECC memory and is passively
cooled. And it's very cheap compared to most systems that people
recommend for running OpenSolar
36 matches
Mail list logo
